delete_account_email

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses the 'cannot remove primary' constraint, which is valuable safety information, and 'Remove' implies a destructive action. Yet it does not mention reversibility, required permissions, or failure behavior, leaving some ambiguity for a deletion tool.

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 that immediately conveys the action and the main constraint. It is concise with no redundant words, earning a perfect score for structure.

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 tool's simplicity—one required parameter, no output schema, no nested objects—the description covers all essential information. It states the action, the target, and a critical constraint, making it complete for effective use.

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 description covers the single parameter email_id at 100% ('Email record ID'), so the baseline is 3. The description adds 'delivery email recipient' context, which clarifies the entity type but does not add syntax, format, or additional semantic detail beyond what the schema already provides.

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 uses the specific verb 'Remove' and the resource 'delivery email recipient', which clearly states the tool's function. It also distinguishes itself from sibling tools like add_account_email and list_account_emails by implying a deletion operation, and the 'cannot remove primary' constraint adds specificity.

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 clearly implies when to use this tool (to delete a delivery email recipient) and provides a key exclusion (cannot remove primary). However, it does not explicitly mention alternatives such as add_account_email or provide contextual guidance beyond the primary constraint, which would make it more complete.

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