trello_update_card

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

No annotations provided, yet the description fails to reveal behavioral traits such as idempotency, side effects, or authorization needs. It does not state what happens to omitted fields or the response format.

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, efficient, and front-loaded. While concise, it could expand slightly on behavior without losing brevity.

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?

Given 9 parameters, no output schema, and no annotations, the description provides a basic overview but lacks details on return value, error states, and full parameter list. Adequate but not comprehensive.

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%, so description must compensate. It lists seven of nine parameters but omits 'start' and 'dueComplete', and does not explain the format or constraints for any parameter beyond their names. Minimal value added.

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 description explicitly states 'Update a card' and lists specific fields (name, description, due date, labels, list, archive state), making it clear what the tool does and distinguishing it from creation or deletion tools.

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 versus siblings like trello_archive_card or trello_move_card, which could be used for subset actions. No when-not-to-use or prerequisite information.

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