existdb_delete_resource

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

Since no annotations are provided, the description carries the full burden of disclosing behavioral traits. It clearly states 'deletion is permanent', which is a critical destructive characteristic. However, it does not disclose other relevant behaviors such as authentication requirements, whether collection deletion is recursive, or what happens on failure. The permanent-deletion warning provides meaningful transparency but leaves gaps.

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 two sentences: the first states the action and target, the second provides a critical warning. Both are essential and free of fluff, making it appropriately concise and 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 destructive operation with four parameters and no output schema, this description is inadequate. It does not explain auth parameters, the need for an endpoint, or the behavior when deleting a collection (e.g., non-empty). Given the complexity and the lack of rich schema/annotations, the description is incomplete for an agent to invoke the tool 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 only 25% (only 'path' is described), and the description adds no parameter semantics. It does not explain the 'endpoint', 'username', or 'password' parameters, nor their roles in the deletion. The description contributes nothing beyond the schema's minimal path description, failing to compensate for the low 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 states a specific verb ('Deletes') and resource ('document or collection from eXist-db'), clearly distinguishing it from sibling tools that list, search, store, or execute. The name and description align perfectly, leaving no ambiguity about the tool's function.

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 only warns 'Use with caution' but provides no guidance on when to use this tool versus alternatives (e.g., when a collection is non-empty, or the need for prerequisites like authentication). It does not mention any exclusions or specific user scenarios, so the usage guidance is minimal.

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