rename_node

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

The description states the basic mutation (naming) but provides no behavioral context beyond that: no mention of side effects, whether it affects text content, return values, or access requirements. With no annotations, the description carries the full burden but doesn't carry much.

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?

One concise sentence with no fluff. It is front-loaded and easy to parse. However, it is so minimal that some usage guidance could have been added without losing conciseness.

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 two-parameter operation with fully documented parameters, this is minimally viable. However, it fails to clarify the distinction between renaming a node and editing text content, and it doesn't mention any output or side effects, so an agent could still invoke it in ambiguous contexts.

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%, and the parameter descriptions ('New name' and 'Target node') are clear enough. The tool description adds no parameter-level detail, but the schema already handles that, so the baseline score is 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 uses a specific verb and resource ('Rename a node'), making the core action clear. It distinguishes from obvious siblings by focusing on the name, but does not explicitly differentiate from tools like batch_rename or set_text_content.

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 is given about when to use this tool versus alternatives like batch_rename, modify_node, or set_text_content. The description leaves the selection criteria entirely implicit.

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