remove_phone

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 authentication prerequisites, the need to establish a session, and the possibility of 2FA verification. It does not detail irreversibility or side effects, but 'remove' plus the 2FA warning gives adequate behavioral context for a simple delete-style tool.

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 compact and front-loaded: the core action appears in the first sentence, followed by essential access and 2FA context. Every sentence adds necessary information without padding or repetition.

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 one-parameter removal tool with no output schema, the description is largely complete: purpose, parameter, access requirements, and 2FA caveat are all present. It does not mention what happens after removal or whether the removed phone could be a primary phone, but those are edge details rather than critical missing instructions.

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 already provides 100% coverage for the single 'id' parameter as 'Phone record ID'. The description adds 'by ID' but no additional format, provenance, or usage detail. This is the baseline score when the schema is already complete.

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 states a specific verb and resource: 'Remove a phone number from the account by ID.' This clearly distinguishes the tool from siblings like remove_email and list_phones. The purpose is immediately understandable without relying on the tool name alone.

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 access context: a Proof account is required, and the user must either set PROOF_API_KEY or sign in via start_login before calling the tool. It also notes that 2FA may be required. It does not explicitly name alternatives or exclusion conditions, so it stops short of a 5.

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