remove_party_email_address_by_id

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

No annotations provided, so description carries full burden. It discloses idempotency on retry, response shapes for fresh vs already removed, no confirmation gate, and server-side metadata discard. This is comprehensive behavioral transparency.

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 a single dense paragraph but each sentence adds value. Could benefit from bullet points or clearer separation of ideas, but it remains reasonably concise for the amount of information provided.

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?

Despite no output schema, the description fully explains response shapes for both success and already-removed cases. Covers preconditions, idempotency, and side effects. Completes the picture for a removal 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?

Schema coverage is 50% (emailAddressId described in schema, partyId not). Description adds meaning by explaining how to obtain emailAddressId from get_party and clarifies that partyId is required. It partially compensates for the schema gap.

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 explicitly states 'Remove one email-address entry from a party by its row id', with a specific verb and resource. It clearly distinguishes from sibling tools like remove_party_address_by_id and remove_party_phone_number_by_id by targeting only email addresses.

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?

Provides explicit when-to-use: when you have the emailAddressId from get_party. Includes 'replace an existing entry' workflow and mentions alternative add_party_email_address for re-adding. No when-not-to-use needed.

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