db_setup_remove

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

No annotations, so description carries full burden. Describes the operation as mutating and advises user confirmation, which discloses the essential behavioral trait. Lacks details on idempotency or failure cases but is adequate.

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?

Two sentences, front-loaded with action and relationship to sibling, followed by usage warning. No extraneous text; every sentence serves a purpose.

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?

Covers primary action, relationship, and usage warning. Missing output description, but given no output schema and tool simplicity, this is acceptable. Almost complete for a mutating tool with high schema coverage.

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 100%, so baseline is 3. Description does not add meaning beyond what is already in parameter descriptions (e.g., instance_id, delete_secret). No extra context provided.

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?

Description clearly states the tool removes an instance's db_profile and stored DB secret, and explicitly positions itself as the undo for db_setup_save. This provides a specific verb and resource, and distinguishes it from a sibling tool.

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?

Provides explicit instruction to confirm with the user before calling (mutating operation) and identifies it as the undo for db_setup_save, giving clear context for when to use. Does not explicitly discuss alternatives or exclusions but is sufficient.

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