Create Kanban Card

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations indicate mutation (readOnlyHint=false) and non-idempotent behavior. The description adds value by detailing HTML content rules and optional checklist steps, but does not disclose other behavioral traits like authentication requirements, side effects, or limits.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise, starting with purpose, then providing necessary HTML rules. The rules block is somewhat lengthy but justified by the complexity of formatting.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The description lacks essential context: it does not explain how to obtain bucket_id or column_id, what the return value is (likely a card object), or prerequisites. For a create tool, this information is critical.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

With 63% schema description coverage, the description provides meaningful HTML rules for the 'content' parameter and mentions 'optional checklist steps' aligning with the 'steps' parameter. However, it does not add significant meaning for other parameters beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The title and description clearly state the verb-resource pair 'Create Kanban Card' and distinguish it from siblings like list, move, and update kanban card tools. The description specifies the action and optional checklist steps, leaving no ambiguity.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when to use this tool (to create cards in a kanban column) and is differentiated from sibling tools like basecamp_create_todo by mentioning 'kanban column'. However, no explicit when-not-to-use or alternative tools are stated.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.