rename_collection

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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the bar is lower, but the description adds almost nothing beyond the name. It never explains the `drop_target` flag, which implies overwriting an existing collection, nor whether indexes, data, and metadata survive the rename.

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?

A single tight sentence with no filler and the scope constraint front-loaded. It is efficient, but the terseness comes at the cost of the missing behavior detail rather than being deliberately minimal.

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 five-parameter mutation with no output schema and no annotation coverage of the drop_target risk, the description leaves the agent without enough to call it safely. Overwrite semantics and target-database selection are the key omissions.

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 0% across five parameters, and the description only implicitly covers `collection` and `new_name`. The potentially destructive `drop_target` boolean and the `database`/`connection` targeting parameters go entirely unexplained.

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 (collection) plus a scoping constraint ("within the same database"), which distinguishes it from create_collection and drop_collection. It does not name a sibling explicitly, but the action itself is unambiguous.

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 rename versus creating a new collection and copying data, no prerequisites, and no warning about what happens if the new name already exists. The only hint is the implicit constraint that the rename cannot cross databases.

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