delete-database-service

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

No annotations provided; description only says 'delete' without explaining destructive behavior, whether it's reversible, or what happens to associated resources. The optional parameters (hardDelete, recursive) are not described.

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?

Single sentence is very concise, but it lacks substance. While not verbose, it omits important details, making it inefficient for an agent.

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?

Given no output schema, no annotations, and low schema coverage, the description fails to provide sufficient context. An agent cannot infer behavior of the boolean parameters or the outcome of deletion.

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 coverage is only 33% (only 'id' described). Description adds no meaning to 'hardDelete' or 'recursive' parameters, which are crucial for agent to understand the tool's behavior.

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 tool deletes a database service (verb+resource). It distinguishes from sibling delete-* tools by specifying 'database service', but lacks additional context about scope or entity type.

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 on when to use this tool versus alternatives (e.g., update-database-service, other delete tools). No mention of prerequisites or conditions for deletion.

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