pbs_s3_client_delete

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

Without annotations, the description fully discloses mutation, risk level, destructive effects (irreversible credential loss, cascading breaks), synchronous execution, dry-run behavior, and return format. No omissions.

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?

Every sentence adds value, with clear structure: mutation label, risk, behavior, undo, pre-req. Slightly lengthy but not verbose; could be more compact.

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 behavior, consequences, return format, and prerequisites. Lacks error handling details, but overall sufficient for a mutation with dry-run pattern.

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. The description adds workflow context for confirm (dry-run vs execution) and digest (optimistic lock), enhancing understanding beyond the schema.

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 starts with 'MUTATION: delete a PBS S3 client configuration,' clearly stating the verb and resource. It distinguishes from siblings by comparing to pbs_remote_delete and mentioning recreation with pbs_s3_client_create.

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?

Explains when to use (delete operation), dry-run vs confirm execution, and warns about breaking datastores/sync configs. Prerequisites (PROXIMO_PBS_* config) are stated, though explicit 'when not to use' is absent.

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