trello_get_card

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

With no annotations, the description must fully disclose behavior. It indicates a read-only operation by stating 'Get full card details', but omits any mention of potential limitations, permissions required, rate limits, or whether the returned data is exhaustive. Minimal additional transparency beyond the basic action.

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, concise sentence that directly states the tool's purpose without superfluous words. Front-loaded with the essential information.

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 the tool's simplicity (2 params, no output schema), the description covers the return value moderately well by listing included items. However, it lacks usage guidance, behavioral details, and parameter semantics, leaving room for ambiguity about the full scope and usage context.

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 50% (only cardId has a description). The description does not add meaning for the format parameter, and for cardId it merely paraphrases the schema. It fails to clarify acceptable values, where to obtain the ID, or how format affects output.

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 the verb 'Get' and resource 'full card details', listing included attributes (comments, checklists, etc.). It effectively distinguishes from siblings like trello_get_card_comments (only comments) and trello_get_board (board-level).

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 use for retrieving comprehensive card details, but lacks explicit guidance on when to choose this over alternative tools (e.g., trello_get_card_comments for only comments). No when-not-to-use or prerequisites mentioned.

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