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

With no annotations, the description carries the full burden. It usefully discloses the result cap ('up to 200'), which is real behavioral information an agent needs for planning. However, it says nothing about the access_token requirement, throttling, pagination, or how results are ranked/truncated when the cap is hit.

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 dense sentence that front-loads the filters and then states the result cap and use cases; nothing is padded. The cryptic 'PRO.' prefix is the only wasted token.

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 six-parameter search tool with no annotations and no output schema, the description covers filters and the result ceiling but omits the authentication flow and the meaning of the organizations_only toggle. Adequate to invoke, but short of fully self-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 coverage is only 17% (just access_token), so the description must compensate, and it largely does: it explains that specialty is taxonomy text with concrete examples ('Dentist', 'Physical Therapist') and that city/state/ZIP combine as a location filter. The one gap is organizations_only, which appears in the schema with no explanation anywhere.

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 names the resource (providers) and the two selection axes (specialty taxonomy plus city/state/ZIP), which makes the operation immediately understandable. It does not differentiate against siblings such as npi_lookup or batch_verify, and the leading 'PRO.' token is opaque, but the core purpose is unambiguous.

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?

'for recruiting, sales and referral networks' hints at the use cases, which is more than nothing, but there is no when-not guidance and no routing to npi_lookup for single-provider lookups or batch_verify for bulk validation. The agent must infer that this is the discovery/sourcing tool versus the verification siblings.

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