Api integrations configs destroy

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered structurally. The description adds nothing beyond that: it does not say whether the delete is permanent, whether linked sync mappings or remote objects are cascaded/removed, or what happens on a nonexistent id. It does not contradict annotations, but it earns little credit.

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?

One short sentence with no padding, but it is boilerplate rather than front-loaded specificity. Conciseness is achieved through omission of the information that matters, not through tight writing.

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 single-record endpoint with no output schema and an undocumented parameter, the description needs to carry the weight and does not. In a namespace with hundreds of near-identical CRUD siblings, an agent has almost nothing here to confirm it is calling the right delete endpoint.

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 required parameter `id` has 0% schema description coverage, so the description was the only place to explain that it is the identifier of the Integration Configuration to remove. It says nothing about the parameter, leaving the agent to infer format and whether it accepts a UUID or numeric id.

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 names the resource ("Integration Configurations") but bundles four distinct operations (create, view, update, delete) into one sentence, so it never states that this particular tool deletes a single config. Against siblings like integrations_configs_create, _update, _retrieve, and _destroy it gives no way to tell which verb this endpoint performs without reading the tool name.

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?

There is no when-to-use guidance, no mention of prerequisites or permissions, and no pointer to alternatives such as partial_update or batch_action. The only hint that deletion is involved is the word "deleting" buried in a list of four operations.

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