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

Annotations already mark as destructive (destructiveHint=true). Description adds detail: consent revocation, data deletion, and return of re-connection URL, enhancing understanding of side effects.

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 value: main action, consequence, and possible reconnection. Front-loaded and no filler, though could be more structured with parameter guidance.

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?

While the outcome is described (data unavailable, returns URL), the single required parameter 'item' is not explained. No output schema exists, and the description does not cover what the parameter represents or how to obtain it.

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 input schema has a single parameter 'item' with no description (0% coverage). The description mentions 'specific bank' but does not clarify the format or source of the parameter, leaving ambiguity.

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?

Clearly states it revokes consent and deletes connection data for a specific bank. Differentiates from sibling tools like openfinance_list_connections (list) and openfinance_force_sync (sync).

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?

Describes the action but does not provide explicit guidance on when to use this tool versus alternatives (e.g., when not to use it or prerequisites like having an existing connection).

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