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

No annotations are provided, so the description carries the full behavioral burden. It lists feature areas, but says nothing about data sources, permissions, rate limits, cost/latency of the multi-source pivots, or whether the WhatsApp/Telegram/Signal lookups are passive or intrusive.

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?

A single compact line with no filler, front-loaded with the resource and the enumerated capabilities. It is efficient; it simply does not spend any words on routing or input format.

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?

The presence of an output schema means return values need not be explained. However, for a multi-source aggregation tool with a completely undocumented input parameter and no usage routing among a dozen phone-related siblings, the description is not yet sufficient.

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?

Schema description coverage is 0% for the single 'q' parameter, and the description never states what form the input takes (E.164, national format, digits only) or what an empty default produces. The parameter is effectively undocumented in both schema and description.

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 tagline names a concrete resource (phone number intelligence) and enumerates the specific surfaces it covers: validity, carrier, region, messaging-app pivots, and caller-ID. That is more specific than a tautology, but it offers no differentiation from siblings like phone, phonepivot, phonespam, or phonespam, so an agent cannot tell which of those to prefer.

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?

There is no when-to-use guidance, no exclusions, and no mention of the many sibling tools (phone, phonefmt, phonenanp, phonepivot, phone_leak) that overlap with this one. The agent must guess whether this is a cheap lookup or the exhaustive aggregate call.

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