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

Annotations already flag destructiveHint=true and readOnlyHint=false, and the description adds meaningful context beyond that: it counts against the free plan's 5-owned-board limit, a side effect an agent cannot infer from structured fields. It does not discuss permission requirements or failure modes, so it is useful but not exhaustive.

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?

Two sentences, action first, usage detail second; no filler. The inline export-path parenthetical is dense but load-bearing rather than decorative.

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?

For a single-parameter import with no output schema and annotations covering the safety profile, the description supplies the payload composition, the input-acquisition path, and the quota side effect. Return value details are not needed since no output schema exists.

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 one parameter at 100% schema coverage, the baseline is 3. The description earns the bump by explaining what the JSON should contain and where to get it, going beyond the schema's 'whole Trello export, as JSON text (max 20 MB)'.

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?

Specific verb+resource: 'Creates a board from a Trello JSON export,' which unambiguously separates it from create_board, duplicate_board, and import-style siblings. It further enumerates the imported payload (lists, cards, dates, labels, checklists, comments, links), so an agent understands the scope of the operation.

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?

Tells the agent exactly how to obtain the required input ('Menu → Print, export and share → Export as JSON') and notes the free-plan quota of 5 owned boards, which is a real selection constraint. It stops short of explicitly contrasting with create_board or duplicate_board for the case where no Trello export exists.

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