card_builder_update_card

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

Discloses partial update behavior but fails to mention idempotency, return value, or side effects. No annotations provided, so the description carries the full burden, yet it is insufficient for a mutation tool with 7 parameters.

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?

Single sentence, very concise but overly minimal. While front-loaded with the main action, it sacrifices necessary detail.

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?

Output schema exists but is not shown; description should still clarify prerequisites (card must exist) and behavior. For a partial update tool with many parameters, much context is missing.

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?

Schema coverage is 0% and the description adds no parameter details. The agent gets no help understanding the meaning of card_id, name, config, tags, categories, or skip_version_bump.

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?

Clearly states the verb 'Update' and the resource 'existing card', distinguishing it from sibling tools like create_card and delete_card. The phrase 'Only the provided fields are changed' further clarifies the partial update behavior.

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?

No guidance on when to use this tool vs alternatives (e.g., create_card for new cards, get_card for reading). No context on prerequisites or when not to use.

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