rename_collection

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

With no annotations, the description carries the full burden and does well: it discloses the link-rewriting side effect, the conditional name change and which reference forms get rewritten versus preserved, explicit refusal conditions (existing destination, nested collection, duplicate name), and what dry_run returns. It omits permission/auth requirements and whether the move is reversible, keeping it from a 5.

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 dense but every clause adds a real behavioral fact (link rewriting, name derivation, refusal cases, dry_run), and the core action is front-loaded. It is longer than typical but not padded.

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 3-parameter mutation tool with no annotations and no output schema, the description covers the important semantics: side effects, name-change rules, refusal conditions, and dry-run behavior. The main remaining gap is the meaning of the `collection` identifier and the shape of the dry-run plan.

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 only 33%: only 'to' is documented in the schema, leaving `collection` and `dry_run` bare. The description compensates for dry_run ('returns the plan') and implicitly for 'to' via 'destination', but never explains what `collection` accepts, so half the parameters remain ungrounded in both places.

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 and resource ('Move a collection to a new folder') and immediately clarifies that the move also rewrites relative links and may change the collection's name, which explains why a tool named rename_collection actually relocates folders. It does not explicitly contrast itself with siblings like update_collection or create_collection, so it stops short of a 5.

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 implies usage through its behavioral detail (link rewriting, name-change side effects, refusals) and mentions dry_run, but never states when to choose this tool over update_collection or how to recover from a refusal. Guidance is inferable rather than explicit.

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