batch_rename_nodes

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

Beyond the annotations (readOnly=false, destructive=false), the description adds that missing nodes are skipped and that it returns { ok, affected }. This provides useful behavioral context about partial handling and the return shape.

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 two sentences long, front-loads the core action, and every sentence adds value: the batch action, the input format, the skipping behavior, and the return value. No extraneous text.

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 simple batch rename tool, the description covers the essential aspects: input format, behavior for missing nodes, and the return value. It doesn't discuss error handling, but given the tool's simplicity and the annotations, this is adequate.

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?

Although schema coverage is 100%, the description reinforces the parameter structure by stating 'from a [{ nodeId, name }] list', which adds clarity about the exact expected array elements beyond the schema's generic 'Per-node rename instructions'.

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 clearly states 'Rename many nodes at once', specifying the verb and resource, and distinguishes itself from the sibling 'rename_node' by emphasizing the batch aspect. It also describes the input list format and the behavior of skipping missing nodes.

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?

The description provides clear context for use: 'many nodes at once' signals this is for batch operations. It doesn't explicitly mention alternatives or when not to use it, but the purpose is clear enough to guide selection in most cases.

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