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

Beyond the annotations (idempotentHint, readOnlyHint=false), the description explains that expected_rev provides optimistic concurrency and that request_id is an idempotency key with a strict reuse rule. It also states 'No provider call or charge', which is operationally meaningful cost information an agent cannot infer.

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 short sentences, action first, then the idempotency rule, then the cost note. No filler.

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?

A mutation tool with no output schema is well covered: precondition, idempotency, and cost are all stated. What remains unstated is the failure mode on a stale expected_rev and what the response contains (e.g. new rev), which would help agents sequence follow-up calls.

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 0% schema description coverage the description carries the burden: it explains expected_rev (revision guard), request_id (idempotency key scope), project_id (must be an owned project), and name (the target value). Length limits remain undocumented but are in the schema.

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?

States a specific verb (rename) and resource (owned Canvas project) plus the concurrency precondition (at expected_rev). The verb is unique across the sibling set of canvas tools, so an agent can pick it without opening the schema.

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?

Constrains correctness use of request_id ('reuse only for the exact same name') and implies the ownership prerequisite. It does not mention alternatives (e.g. canvas_update_node) or what to do on revision conflict, so no explicit when-not guidance.

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