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

Annotations already mark destructiveHint=true, but the description adds meaningful context: the deletion is a soft-delete and the account is merely deactivated, not permanently removed. It also discloses that a confirmation is returned. No contradiction with annotations exists.

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?

The description is compact and well-structured with Description, Args, and Returns sections. Every sentence adds information, and the soft-delete clarification is front-loaded. No redundant or filler 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?

For a single-parameter tool with destructive annotations and no output schema, the description covers the essential behavior: soft-delete, deactivation, and confirmation. The return specification is somewhat vague ('Confirmation of deletion'), but given the low complexity and annotations, the definition is reasonably complete.

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 schema provides only the name and type for account_id (integer), and schema description coverage is 0%. The description's Args section states 'account_id: The account ID to delete,' which adds minimal semantic context but largely restates what the parameter name already implies. For a single simple ID, this is acceptable but not rich.

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 states a specific verb and resource: 'Delete (soft-delete) a financial account.' It clearly distinguishes the action from permanent deletion by explaining the account is deactivated, not permanently removed. The title 'Accounts: Delete account' reinforces the resource without ambiguity.

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?

The description implies usage through the tool name and the phrase 'Delete a financial account,' and it clarifies the soft-delete semantics. However, it does not explicitly name alternatives (e.g., update_account) or state when not to use this tool, so selection guidance is only implicit.

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