cigchat_clear_integration_dropi

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

No annotations are provided, so the description fully owns behavioral disclosure. It clearly labels the operation as 'DESTRUCTIVE: irreversible', explains the two-step confirmation mechanism, and states the auth requirement. This is exemplary for a destructive mutation tool.

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 sentences, each adding distinct value: purpose, destructive warning, and usage instructions. The front-loaded danger warning is highly effective, and there is no redundant text.

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 annotations and no output schema, the description covers all essential context: what it does, that it's irreversible, how to invoke safely, and what permissions are required. It is fully self-sufficient for safe usage.

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 single 'confirm' parameter is fully described in the schema, so the description adds little beyond referencing the flow. Schema coverage is 100%, meeting the baseline. The description's mention of 'confirm' reinforces but doesn't extend the schema semantics.

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 uses a specific verb-resource pair: 'Clear the config of Dropi integration'. This clearly distinguishes it from sibling tools like cigchat_clear_integration_shopify or cigchat_set_integration_dropi. The HTTP DELETE method adds further precision.

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?

Explicitly instructs the caller to invoke without 'confirm' first to receive an impact statement, and only then pass the token after human approval. Also specifies the required auth scope ('Manage Team'). This is strong when-to-use/sequence guidance.

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