pbs_acme_account_delete

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

Discloses irreversible mutation, dry-run default, high-risk TLS lockout, account key destruction, force behavior, and synchronous return null. No annotations provided, so description carries full burden and meets it comprehensively.

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?

Description is dense but well-structured, starting with key warning. Every sentence adds value, though slightly verbose with multiple parenthetical asides. Minor room for tighter phrasing.

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 high-complexity irreversible mutation tool, description covers dry-run behavior, risks, parameter nuances, and return format. Output schema exists, so return details are not required. Highly 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?

Schema coverage is 100%, baseline 3. Description adds value by explaining that confirm=False returns dry-run plan, force deletes local even if CA refuses, and proximo_target selects target. Provides context beyond schema.

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?

Description clearly states specific verb and resource: 'DEACTIVATES an ACME account at the CA ... and deletes the local record.' Distinguishes from siblings like pbs_acme_account_create by noting that re-registering creates a different account.

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?

Explicitly mentions when to use (deleting an ACME account), high-risk scenario (TLS lockout if only account), dry-run default, and alternative tool for creating a new account. Provides explicit 'when-not' context.

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