update_card

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

Discloses that patch.columnId moves the card and done:true marks completion, but omits side effects like notifications, permissions, or reversibility. With no annotations, the description carries full burden and provides only partial behavioral context.

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?

Two sentences with no wasted words. Front-loads purpose, then provides critical usage nuance. Every sentence earns its place.

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?

Covers core update behavior and two key fields, but doesn't explain all 9 patch fields, return values (no output schema), or interaction with sibling tools. Adequate for basic use but lacks full guidance for complex scenarios.

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?

Adds meaning to key parameters (columnId, done), but the schema has 9 optional fields in patch, and many (e.g., deadline, priority, parentCardId) are left unexplained. Schema coverage is 0%, so description compensates partially but insufficiently.

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?

Description clearly states 'Update card fields', specifies the key operation of moving cards via patch.columnId, and distinguishes from sibling tools like create_card or archive_card by focusing on updates.

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?

Provides a useful tip to omit unchanged fields, but lacks explicit guidance on when to use this tool versus alternatives (e.g., archive_card for archiving, create_card for new cards). No when-not-to-use or exclusion criteria.

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