Delete account

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

Annotations already disclose destructive behavior (destructiveHint=true), non-read-only status (readOnlyHint=false), idempotency, and open-world effects. The description simply confirms deletion without adding extra context such as irreversibility, cascading effects, or permissions. No contradiction with annotations, but no additional behavioral transparency.

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 a single, front-loaded sentence with zero wasted words. It directly conveys the action and target resource, making it efficient and easy to parse.

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?

The tool is simple with one required parameter, annotations cover destructive/idempotent behavior, and an output schema exists. The description is adequate for basic invocation, but it omits potentially useful context such as whether deletion is permanent or affects related data, which would make it fully 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 input schema fully documents account_id with a description referencing get_accounts, and schema description coverage is 100%. The description's 'by ID' adds no additional semantic meaning beyond what the schema already provides, so the baseline of 3 is appropriate.

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 ('delete') and resource ('Monarch account') and the identification method ('by ID'), making the action unambiguous. It clearly distinguishes from sibling tools like create_manual_account and update_account, which are lifecycle operations.

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 does not specify when this tool should be used instead of alternatives such as update_account or create_manual_account. It gives no conditions, prerequisites beyond having an ID, or exclusions, leaving usage to inference.

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