delete_database_service

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only states 'Delete,' which implies destruction but does not explain the meaning of the flags (hard_delete, recursive) or whether deletion is reversible. The behavioral implications of soft vs. hard delete and cascade deletion are omitted.

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 extremely concise (one sentence), but it sacrifices informativeness. While brevity is good, the sentence does not earn its place because it merely echoes the tool name without elaboration. It could be restructured to include key parameter notes.

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 the tool has three parameters, no output schema, and no annotations, the description is severely incomplete. It does not cover deletion behavior, flag semantics, or expected outcomes. An agent would lack critical context to use this tool correctly.

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?

The input schema has 0% description coverage, and the tool description fails to explain any parameters. service_id, hard_delete, and recursive are not described. The schema titles offer minimal hints, but the description adds no value beyond that. For a tool with three parameters, this is inadequate.

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 'Delete a database service,' which identifies the verb (delete) and resource (database service). This distinguishes it from sibling tools that delete other entities like bots, charts, or tables. However, it lacks nuance about scope or effects.

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 on when to use this tool versus alternatives, such as update_database_service for modifying instead of deleting, or whether prerequisites exist. The description does not mention the hard_delete or recursive flags, which are critical for deciding usage.

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