Remove an index from a collection schema by specifying the collection and index name. Solves schema cleanup and maintenance by deleting unwanted indexes.
Remove an index from a collection schema
| Name | Required | Description | Default |
|---|---|---|---|
| indexName | Yes | Name of the index to remove | |
| collection | Yes | Collection name |
Changes observed during successful MCP inspections.
v0.1.7Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It communicates a destructive action via 'Remove', but does not mention persistence, irreversibility, schema-wide effects, permissions, or error behavior.
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 concise sentence with no filler. The primary action and object are front-loaded.
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 two-parameter destructive operation with complete schema coverage, the description is adequate. However, because there is no output schema and no annotations, a bit more detail on effects or implications would improve completeness.
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 already fully documented. The description adds minimal semantic context by mapping 'index' and 'collection schema' to the parameters, but does not go beyond the schema.
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 states a clear action ('Remove') and a clear resource ('an index from a collection schema'). It is semantically distinct from sibling baasix_add_index, though it does not explicitly name the sibling.
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 use this tool versus alternatives, no prerequisites, and no explicit exclusions. The description only restates the action, leaving the agent to infer usage context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.