delete_blacklist

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

With no annotations, the description discloses non-idempotency, error behavior for non-existent numbers, and effect on send-sms delivery. Missing auth or rate limit details, but adequate for this simple 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?

Two concise sentences plus a reference link. No filler, front-loaded with essential info.

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 simple tool with one parameter, no output schema, and no annotations, the description is complete: it explains purpose, behavior, non-idempotency, and provides a reference.

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 already describes the number parameter with accepted formats. The description adds 'One number per request' but no additional parameter meaning beyond the schema, which has good coverage.

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 clearly states it removes a phone number from the account's blacklist, specifies 'one number per request', and distinguishes from sibling tools like add_blacklist and get_blacklist.

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 says when to use (to remove a number) and provides a caveat about idempotency (not idempotent, returns error if not on list). It does not explicitly compare to alternatives but context implies usage.

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