Astra DB MCP Server

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It states this is a destructive delete operation but doesn't mention permissions required, whether deletions are permanent/reversible, error handling for invalid IDs, or any rate limits. For a destructive bulk operation, this is inadequate disclosure.

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?

Extremely concise single sentence with zero wasted words. Every element ('Delete multiple records', 'from a collection', 'at once') contributes essential information. The structure is front-loaded with the core action.

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 bulk operation with no annotations and no output schema, the description is insufficient. It doesn't address critical context like what happens on partial failures, whether deletions are atomic, what confirmation (if any) is required, or what the response contains. The 100% schema coverage helps but doesn't compensate for missing behavioral transparency.

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 the schema already fully documents both parameters (collectionName and recordIds). The description adds no additional parameter context beyond what's in the schema, maintaining the baseline score for high schema coverage.

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 ('Delete multiple records') and resource ('from a collection'), making the purpose immediately understandable. It distinguishes from sibling DeleteRecord by specifying bulk operation, though it doesn't explicitly contrast with DeleteCollection which deletes entire collections rather than records.

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 about when to use this tool versus alternatives like DeleteRecord (for single deletions) or DeleteCollection (for entire collection removal). The description mentions 'at once' which implies efficiency for multiple deletions, but lacks explicit comparison or prerequisites.

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