Rename item

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

The destructiveHint=false annotation already tells the agent this is a non-destructive operation, so the description only needs to add context beyond that. It does add the meaningful 'same parent' constraint, but says nothing about collision behavior — e.g. whether renaming to an existing name fails, overwrites, or auto-suffixes — which is the key behavioral unknown for a rename tool.

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?

Two sentences, zero filler, with the scope constraint front-loaded and the alternative routing second. Every clause earns its place.

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 two-parameter, no-output-schema operation, the description covers purpose, scope, and the sibling alternative adequately. The only real gap is the undefined behavior when the target name already exists.

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%, so both parameters (path, newName) are already documented in the schema, including the important 'not a path — just the name' clarification. The description adds no parameter detail beyond that, so the baseline 3 applies.

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 (file or folder), plus the scoping constraint 'in place (same parent)', which distinguishes it from a move operation. An agent can identify this tool 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?

Explicitly names the alternative ('To change folders use drive_move') and the condition that selects it. The when-not guidance is unambiguous, which is unusually strong for a sibling set this large.

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