trello_get_card_checklists

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

With no annotations, the description only states it retrieves checklists and items. It does not disclose potential behavior like empty result handling, pagination, or error conditions. Adequate but minimal for a read operation.

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?

A single sentence that is concise and front-loaded. No redundant words. Could be slightly expanded to add useful context without becoming verbose.

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?

Lacks information about the return format, especially since there is no output schema. Does not explain how to use the fields parameter or that checkItems defaults to 'all'. Incomplete for an agent to fully understand the tool's behavior.

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?

All parameters are fully described in the input schema (100% coverage). The description adds no additional meaning or context beyond what the schema already provides, e.g., it doesn't clarify the effect of the checkItems or fields parameters.

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 action ('get') and resource ('all checklists and their items for a specific Trello card'). Distinguishes from sibling tools like trello_get_checklist (single checklist) and trello_get_check_item (single item).

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 such as trello_get_checklist or trello_get_check_items. Does not explain when to choose this over other checklist-related tools.

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