List Trello boards

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds important behavioral details: it includes archived boards and scopes visibility to the configured token. It also states the exact return fields (id, name, url, closed). This goes beyond annotations without contradicting them, though it does not mention pagination or rate limits.

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 two sentences, both dense with information. The first sentence states action and scope; the second lists return fields and links to sibling tools. Every word earns its place, and the most important information is front-loaded.

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?

This is a simple read-only list tool with no parameters and no output schema. The description fully covers the scope, return value shape, and relationship to other tools. Nothing important is missing for an agent to invoke it correctly.

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?

With zero parameters, the baseline is 4. The description compensates by clarifying what the result set includes (all token-accessible boards, including archived) and what fields are returned, which adds useful semantics even though no parameters exist.

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 action 'List' and the resource 'Trello boards', and precisely scopes it as 'every Trello board the configured token can see, including archived (closed) ones'. It differentiates from sibling tools by focusing on boards and noting that returned IDs feed other tools like get_lists and get_cards.

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 explicitly tells the agent to 'Start here' and explains how the board IDs feed downstream tools (get_lists, get_cards, get_labels, get_board_activity). This provides clear guidance on when to use this tool as the entry point for many board-related operations.

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