remove_email

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

With no annotations provided, the description carries the behavioral disclosure burden. It discloses the authentication requirement, the need for a Proof account, and the possibility of 2FA verification for sensitive operations. It doesn't detail the response or permanent consequences, but 'remove' clearly implies destructive intent.

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 short and front-loaded with the primary action. The ACCESS block is useful but slightly verbose; it could be tightened. Overall, every sentence contributes meaningful information.

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 single-parameter tool with no output schema, the description covers the essential context: what the tool does, how to authenticate, and that 2FA may be triggered. It leaves out edge cases like whether the email must not be primary or what the success response looks like, but these are not critical for invocation.

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 describes 'id' as 'Email record ID' and marks it required. The description reinforces that removal is by ID but adds no additional semantic detail. With 100% schema coverage, 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 clearly states the action ('Remove'), the resource ('an email address'), and the key qualifier ('by ID'). This distinguishes it from related email tools like list_emails, set_primary_email, and start_add_email without ambiguity.

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 provides clear operational context: it requires a Proof account, explains how to authenticate via API key or start_login, and warns that 2FA may be required. It doesn't explicitly name alternatives or exclusions, but the unique remove-by-ID operation makes the intended usage sufficiently clear.

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