mongo_drop_index

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

With no annotations, the description carries full burden. It discloses the readOnly block but does not explicitly state the destructive, irreversible nature of dropping an index. The name implies destruction, but more explicit behavioral details would improve transparency.

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 waste. The first sentence front-loads the core action, the second adds a key behavioral condition. Every word 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 drop operation, the description covers the action and a condition. However, it omits important context like: index must exist, operation is permanent, and no error behavior if index not found. Also no mention of output (acknowledgment). Adequate but not complete.

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 50%, but the description adds no parameter-level meaning beyond the schema. It mentions 'by name' for indexName but does not clarify database or collection fields. The description should compensate for missing schema descriptions but does not.

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 verb 'Drop' and resource 'an index by name on a MongoDB collection', differentiating it from siblings like mongo_create_index (create) and mongo_list_indexes (list). It also specifies a condition (readOnly mode block).

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 that the tool is used to remove an index when readOnly mode is disabled. It provides context (blocked in readOnly) but lacks explicit when-not-to-use or alternatives. The purpose is clear enough for basic guidance.

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