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

No annotations exist, so the description carries the full burden. It does disclose a real behavioral rule — matches come from two distinct phone sources (practice registry vs. self-published on a claimed page) and withheld numbers are suppressed — which is valuable beyond the schema. It omits what is returned (a provider record vs. a list), whether multiple providers can match one number, and pagination.

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?

Three short sentences with no waste, and the core matching rule is front-loaded. The first sentence is syntactically tangled ('whose registry practice phone, or a phone they published on a claimed page, is this number'), which costs a little readability but not length.

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 lookup with no output schema and no annotations, the description covers input format and one filtering rule but never says what comes back — a single provider, a list of providers, or an empty result when the number is unclaimed. That return-shape gap is the main missing piece for correct invocation/interp retation.

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 is a single required parameter with 100% schema description coverage, so the schema already states 'A US phone number in any format.' The description's 'Any US format' merely restates it rather than adding parsing or normalization detail. Baseline 3 applies.

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 identifies the resource (providers) and the matching criterion (their registry practice phone or a phone published on a claimed page equals this number), which effectively communicates a reverse phone lookup and distinguishes it from lookup_provider (by identity) and search_providers (by other criteria). However, it never states the action as a verb — the agent must infer 'find/look up' from a relative clause.

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 and none of the siblings (lookup_provider, search_providers, nearby_providers) are named as alternatives even though a phone-based lookup overlaps conceptually with provider search. The only constraint given is negative (withheld numbers are excluded), which is a filter, not routing guidance.

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