trello_get_card_checklists

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states 'Get all checklists and their items.' It does not mention that the checkItems parameter can omit items, nor does it explain response structure, error behavior, or permissions. This is minimal transparency for a no-annotation tool.

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?

The description is a single, concise sentence of 11 words that gets straight to the point. It is front-loaded and contains zero filler, making it effective and easy to scan.

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?

Despite having no output schema and no annotations, the description gives only a high-level summary of what is returned. It fails to mention the effect of optional parameters like 'fields' or 'checkItems', nor does it describe the structure of the checklist objects. For a tool with five parameters and no structured output, this is insufficient 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 100%, so all parameters already have descriptions. The tool description adds no additional meaning about parameters beyond the schema; it simply restates the overall purpose. Baseline 3 is appropriate since the description does not enhance parameter understanding.

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 clearly states the tool's function: 'Get all checklists and their items for a specific Trello card.' The verb 'Get' indicates a read operation, and the resource (checklists and items) is specific and distinct from sibling tools like 'get_card' or 'trello_get_card_attachments'. It fully covers the tool's purpose without ambiguity.

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 when to use the tool—whenever you need checklists for a card—but provides no explicit guidance compared to alternatives. There are no exclusionary statements or mentions of when to use a different tool. This is adequate but not enriched, fitting an 'implied usage' score rather than clear guidelines.

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