remove_pin

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

No annotations, so description carries full burden. It discloses the primary-device-only constraint and the exact error message on linked devices. It also warns about the security consequence (anyone with phone number can re-register) and the SIM-swap risk, which is critical behavioral information.

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 four sentences, but each conveys essential information: the action, the constraint, the security warning, and the alternative. It is front-loaded with the core purpose and avoids redundancy.

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 parameterless tool with no output schema, the description is fully complete. It covers what the tool does, when to use it, when not to, what happens on failure, and the consequences. An agent has all information needed to call it 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?

There are zero parameters, so schema is empty and coverage is trivially 100%. Baseline for zero params is 4, and the description doesn't need to explain any parameters. No additional parameter semantics required.

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?

States the specific verb 'Remove' and resource 'Signal Registration Lock PIN', and explains the effect (disabling re-registration protection). It also distinguishes from set_pin by explicitly recommending set_pin for setting a new PIN, making it clear this is for removal only.

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?

Explicitly states when to use: 'Use only if you intentionally want to disable the registration lock.' It also provides the alternative: 'Use set_pin to set a new PIN instead of removing the existing one,' and warns against removal if relying on it for SIM-swap protection. This gives clear decision criteria.

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