remove_party_email_address_by_id

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

Discloses atomicity, reversibility, and metadata discard. Annotations are readOnlyHint:false and destructiveHint:false; description explains non-destructive nature via idempotency and re-add capability. Adds significant context beyond annotations.

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?

Single paragraph, front-loaded with core action. Every sentence adds value, though slightly lengthy. Structure is logical.

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?

Complete for a removal tool without output schema: explains response format, idempotency, reversibility, and side effects. Covers all necessary aspects for an agent to use correctly.

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 covers emailAddressId with description; description adds context for partyId implicitly via tool name and workflow. Overall, description helps understand parameter usage despite 50% schema coverage.

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 specifies removing one email-address entry from a party by row id, using specific verb and resource. Differentiates from sibling tools like remove_party_phone_number_by_id.

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 workflow: use remove to delete an existing email, then optionally add new one with add_party_email_address. Explains idempotency and response behavior, guiding when to retry.

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