remove_party_phone_number_by_id

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

Description states 'Remove' which is inherently destructive, but annotations have 'destructiveHint: false', creating a contradiction. While description explains reversibility and idempotency, the contradiction undermines trust.

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?

Succinctly covers action, reversibility, idempotency, and response format in a few sentences. No unnecessary words; well-structured.

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, description details response format for both fresh removal and already-removed cases. Tool has only 2 params, and all necessary context is provided.

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?

Adds meaning beyond schema: explains phoneNumberId as 'Capsule's id for the phone-number row' and tells agent to read it from get_party. Schema description coverage is 50%, but description compensates.

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 states 'Remove one phone-number entry from a party by its row id.' Specifies verb (remove), resource (phone-number entry), and method (by row id). Differentiates from sibling tools by focusing on phone numbers.

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 guidance: no 'confirm: true' gate, reversible via add_party_phone_number, discover id via get_party. Does not explicitly state when not to use, but enough context for proper use.

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