remove_party_phone_number_by_id

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

No annotations are provided, so the description fully discloses behavior: atomicity, reversibility (no confirm gate), idempotency with two distinct response formats. This covers all key behavioral traits an agent needs.

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 paragraph with clear, front-loaded sentences. It covers all necessary information without extraneous content, though it could be slightly more concise by separating atomicity and reversibility.

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 no output schema, the description explains the response shapes for fresh and repeated removals. It provides enough context for an agent to understand the tool's behavior completely for a simple 2-parameter operation.

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 covers 50% of parameters with descriptions (only phoneNumberId). The description adds meaning by explaining that phoneNumberId is the row id from get_party and that partyId is an integer. It also shows example response structures that clarify parameter usage.

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 phone-number entry from a party by its row id' and distinguishes it from sibling tools that remove other types of entries (e.g., addresses, emails).

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 clear guidance on when to use (to remove a phone number), how to discover the id (via get_party), and notes that it is reversible via add_party_phone_number. Also explains idempotent retry behavior.

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