drop_index

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds one genuinely useful behavioral constraint (the _id index is protected) but is silent on failure behavior when the index doesn't exist and on the performance consequences of removing an index used by queries.

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 short sentences, front-loaded with the action and followed by the discovery pointer and the constraint. No waste.

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 destructive mutation with zero schema documentation and no output schema, the description covers only the _id gotcha. An agent still lacks the target-resolution semantics (which database/connection apply) needed to call it confidently.

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 four parameters, so the description must carry the load — but it only clarifies that `name` is the index name. It never explains how collection pairs with name, nor what the nullable `database` and `connection` parameters default to when omitted.

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 ("Drop an index") and points to list_indexes for discovery. It is clearly distinct from sibling create_index/drop_collection/drop_database, though it doesn't explicitly say so.

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?

Names list_indexes as the way to obtain valid index names and states an explicit exclusion (the _id index cannot be dropped). No guidance on when to drop vs. rebuild an index or what happens to queries afterward, but the selection context is clear.

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