rename_node

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

No behavioral information is disclosed beyond the basic action. With no annotations, the description does not mention whether the rename is persistent, what happens to references, or any side effects, which is a significant transparency gap.

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?

The description is a single sentence, which is terse, but it is under-specified rather than appropriately concise. It omits necessary context, making it too minimal to be effective.

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?

With two required parameters, no annotations, and no output schema, a one-sentence description is grossly insufficient. The agent lacks context about node path conventions, naming rules, or invocation requirements, making the tool description incomplete.

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 coverage is 0% and the description does not explain 'path' or 'new_name'. The agent is left without any understanding of expected formats or constraints, so the description fails to compensate for the missing schema details.

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 'Rename a node' uses a clear verb and resource, aligning with the tool name and distinguishing it from siblings like move_node or delete_node. However, it lacks any detail about scope or context, so it is clear but not rich.

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 use this tool versus alternatives like move_node or set_node_properties. The description provides no context, exclusions, or alternative references, leaving the agent without decision support.

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