customer_delete_request

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

Discloses that the account is flagged for deletion and not immediately removed, but with no annotations, additional behavioral details (e.g., reversibility, email notifications) are missing.

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?

Concisely conveys purpose, effect, and parameter info in a few sentences. No unnecessary words; important points front-loaded.

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?

Explains the main effect and mentions output schema existence (context signal). Lacks prerequisites or error scenarios, but acceptable for a simple tool.

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?

Only one parameter 'email' with a clear description in the text ('Customer e-mail address'). Schema coverage is 0%, so description compensates fully.

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 the tool submits a GDPR account-deletion request for a customer. Highlights that it does not immediately delete, distinguishing it from a hypothetical instant deletion tool.

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 notes GDPR context and that the deletion is not immediate, guiding agents to use this for non-immediate requests. However, lacks explicit comparison to sibling tools or mention of when not to use.

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