drop-index

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

Annotations indicate destructiveHint=true and readOnlyHint=false, which the description aligns with by using 'Drop' (implying mutation and destruction). The description adds minimal context beyond annotations, specifying the database and collection scope but not detailing effects like performance impacts or irreversibility.

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 a single, efficient sentence that front-loads the core action ('Drop an index') and essential parameters. There is no wasted verbiage, making it easy to parse quickly.

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 tool with no output schema, the description is minimal but covers the basic operation. It lacks details on behavioral outcomes (e.g., what happens post-drop, error conditions) and doesn't compensate for the absence of output schema, though annotations provide some safety context.

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 parameters are fully documented in the schema. The description mentions 'database and collection' and 'indexName' but adds no extra meaning beyond schema details like constraints (e.g., minLength for indexName) or the fixed 'type' parameter.

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 the action ('Drop') and target ('an index'), specifying the required database and collection context. It distinguishes from siblings like 'create-index' and 'collection-indexes' by focusing on deletion rather than creation or listing, though it doesn't explicitly contrast with them.

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?

No guidance is provided on when to use this tool versus alternatives. While the purpose implies it's for removing indexes, there's no mention of prerequisites (e.g., ensuring the index exists), consequences, or when to choose other tools like 'collection-indexes' for inspection first.

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