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

Annotations already declare destructiveHint=true and idempotentHint=true, yet the description adds a concrete consequence not encoded anywhere: the billing records the provider supplied are deleted along with the connection. That plus the confirmation requirement gives an agent real decision-relevant behavior, though permanence/restore options remain unstated.

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 short sentences, the destructive effect is front-loaded, and there is no filler. Slight deduction for the ambiguous 'it' that forces the reader back to the title.

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?

An output schema exists so return values need no explanation, and the annotations carry the safety profile. However, for a destructive tool the description omits the parameter format and any note on what depends on the provider (keys, tools, historical attribution), leaving real gaps.

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?

One required parameter with 0% schema description coverage and no enum. The description says nothing about whether 'provider' expects a slug, display name, or ID, so the agent must guess the value format for a destructive call.

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?

States a specific verb (disconnects) plus the consequential effect (deletes billing records brought in from that provider), which distinguishes it from connect_provider. The object is an unresolved pronoun 'it' that only the title supplies, and 'Veqen' is unexplained jargon, so it falls just short of fully self-contained.

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?

'Confirm first' gives a workflow precondition, which is more than nothing. But it never says when to prefer this over alternatives such as connect_provider, list_connections, or shutting off a key, nor what happens to the provider's keys/data afterwards.

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