cigchat_clear_integration_s3storage

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

With no annotations, the description fully discloses the destructive and irreversible nature ('DESTRUCTIVE: irreversible'), the confirmation workflow, and the required auth scope. This is strong behavioral transparency beyond what schema or annotations would provide.

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?

Three concise sentences cover purpose, danger/confirmation workflow, and auth requirement—each earning its place. No fluff or redundancy, fully 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 one optional param and no output schema, the description covers the action, impact, confirmation pattern, and prerequisites. It is sufficiently complete for an agent to invoke correctly without further info.

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 sole parameter `confirm` is already well described in the schema (100% coverage). The description adds meaningful context by explaining the two-step call sequence, which clarifies when and how to use the parameter. This goes beyond a simple schema repetition.

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 a specific verb and resource: 'Clear the config of S3 Storage integration', clearly distinguishing it from sibling get/set integration tools. The explicit HTTP DELETE reference further reinforces the precise action.

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 step-by-step usage guidance: call without `confirm` first to get an impact statement, then pass the confirmation token after approval. It also states the required 'Manage Team' scope. Does not explicitly compare against alternative tools, but the destructive nature makes the workflow guidance highly relevant.

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