archive_customer

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

The description discloses a key behavioral outcome (no longer appears in active listings), but with no annotations provided, it carries the full burden. It does not mention reversibility, permissions, or effects on associated data like invoices. This leaves important behavioral traits undisclosed.

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, short sentence that front-loads the verb 'Archive' and provides the essential outcome. Every word is meaningful, with no redundancy or unnecessary detail.

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?

Given the absence of annotations and an output schema, the description should cover more context to be complete. It fails to mention return values, reversibility, or how archiving differs from permanent deletion (relevant due to the sibling delete_account). The tool is simple, but the description is too sparse to be 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 schema defines a single required 'accountId' parameter with no description. The tool description does not mention the parameter at all, and schema description coverage is 0%. Since the description fails to explain what the ID refers to or how to find it, it offers no additional value beyond the 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?

The description clearly states the action ('Archive') and the target ('a customer account'), and specifies the consequence ('it no longer appears in active listings'). This effectively differentiates it from siblings like delete_account, which would imply permanent removal.

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 a use case: hide an account from active listings. However, it does not explicitly mention when to use this tool versus delete_account or any conditions that would make archiving preferable. The guidance is only implied through the word 'archive' rather than directly stated.

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