deregister_phone

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

With no annotations provided, the description carries full burden for disclosing behavioral traits. It merely says 'Deregister', which implies a destructive or state-changing action, but gives no details about side effects, reversibility, or consequences such as loss of access or impact on WhatsApp Business features. This is a significant transparency gap.

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, focused sentence with no superfluous words. It is appropriately sized for a tool with no parameters and simple purpose, and it front-loads the verb 'Deregister' for immediate clarity.

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?

While the tool itself is simple (no parameters, no output schema), the description lacks context about the implications of deregistering a phone number. It does not explain what happens afterwards, whether the action is reversible, or any warnings about the destructive nature. More context is needed for an AI agent to safely invoke it.

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 input schema has zero parameters, so the baseline is 4 per the guidelines. The description adds no parameter information because there are no parameters, and the schema coverage is trivially 100%. No further compensation is needed.

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 uses a specific verb 'Deregister' with a clear resource 'WhatsApp Business phone number', which immediately distinguishes it from sibling tools like register_phone or get_phone_number. It is direct and unambiguous about what action the tool performs.

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?

No guidance is provided about when to use this tool versus alternatives. There is no mention of prerequisites, such as the number needing to be registered, or exclusions, such as not using it while active conversations are ongoing. The description simply states the action without contextual direction.

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