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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is known without the description. The description adds no behavioral context of its own — no note on whether the old name is recoverable, whether referrers break, or whether permissions are needed for a destructive mutation.

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?

A single short sentence with zero waste and the action front-loaded, but it is under-specified rather than efficient — the same two words could have carried a constraint or an alternative at no cost.

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?

An output schema exists so return values need not be explained, and the schema fully documents the two parameters. Still, for a destructive, idempotent, open-world mutation the description should say what the rename affects or requires; it leaves that entirely to annotations and inference.

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%, including the node ID format example and the meaning of name, so the baseline is 3. The description adds no extra meaning about name uniqueness, length limits, or allowed characters.

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?

"Rename a node" gives a specific verb and resource and implicitly narrows the generic name update_node to name-only mutation, which distinguishes it from update_node_access_rule or update_project. However, it adds essentially nothing beyond the title "Rename node," so it reads as a restatement rather than an explanation.

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?

No guidance on when to use this versus siblings: nothing says whether renaming is preferred over re-creating via create_node/delete_node, and no prerequisites or constraints are mentioned. The agent must infer the context entirely.

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