feat(create-item): add optional description argument

[shaneer]

Summary

• Adds an optional description (markdown string) parameter to the create_item tool
• After item creation, calls set_item_description_content to set the description — applied across all three creation paths (new item, subitem, duplicate)
• Adds a new GraphQL mutation file set-item-description-content.graphql.ts and regenerated types

Test plan

• 6 new tests covering: description set for each creation path, skipping call when not provided, success: false error handling, API error propagation
• All 914 existing tests continue to pass

🤖 Generated with Claude Code

[anyatchernishov]

@shaneer question - in monday dev that would work perfectly. What will happen in WM where item description in not visible by default?

This is what is looks like now when creating an item via MCP in WM board, the description in the update -

After your change, if the user did provide description, where will it go in WM board?

[shaneer]

Good point! I didn't remember that it's not there in wm. I have to test what the API query does in that case but I assume it will fail in which case what I did is not good here.

I wonder if this data is returned in the get board info, if not, it's also a question of what the desired behavior here is. What do we want it to be created if it's not there? Or do we need to separate here into different tools depending on product? Or should it be a skill after all?

I'll check the behavior and let's discuss