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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), but the description adds genuinely new behavior: the operation is free, and it requires authentication via OAuth or a specific Authorization header with a concrete key-creation URL. That auth and cost detail is not derivable from the schema or annotations. It does not, however, address the non-idempotent hint or what happens with a stale revision.

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?

Three compact sentences with the core action front-loaded, followed by cost and auth requirements. The auth sentence is verbose but each clause carries actionable information (two connection paths plus a key URL).

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 low-complexity mutation tool with an output schema and full parameter documentation, the description covers the two things an agent cannot infer elsewhere: cost and authentication setup. Missing only edge-case behavior around the revision parameter and conflict handling.

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 description coverage is 100%, so the schema already explains canvas_id, name (1-100 chars), and the optional revision field. The description adds no parameter-level detail beyond the schema, making the baseline of 3 appropriate.

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 opens with a specific verb and resource ('Rename a board'), which is unambiguous and distinguishes it from siblings like create_canvas, get_canvas, and list_canvases. It never explicitly contrasts itself with update_card or refresh_canvas, so it earns a 4 rather than a 5.

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?

There is no guidance on when to choose this tool over siblings such as update_card, refresh_canvas, or create_canvas, and no stated preconditions like needing an existing board. The cost note ('Costs no credits') is incidental context rather than usage guidance.

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