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

Annotations already cover read-only, idempotent, open-world, non-destructive semantics, so the safety profile is handled. Beyond that the description adds only marketing framing ('FREE beta', 'future paid tier') and the vague 'authoritative API provenance' — it says nothing about latency, rate limits, result completeness guarantees, or how the evidence tier's behavior differs from basic. Annotations do not contradict the description.

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, front-loaded with the beta status. They are compact, but the content is mostly tier/billing framing rather than tool behavior, so the brevity does not buy useful information density.

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?

No output schema, so the description should at least sketch what is returned (recipient records with provenance fields?). Combined with zero parameter documentation and no sibling differentiation against us_recipient_search_basic, the definition is incomplete for an agent deciding whether and how to call this tool.

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%, so the description bears the burden of explaining the query and limit parameters, and it explains neither. It never says what 'query' matches (name, UEI, DUNS, keyword), what the limit cap of 50 means, or that query is required with a 2-100 character range. The only numeric hint is the vague phrase 'larger result set', which is not tied to the limit parameter.

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 title and name establish that this is a recipient search tool with an 'evidence' tier, and the description mentions 'Larger recipient result set with authoritative API provenance.' That's a vague characterization of what makes it different from us_recipient_search_basic — it implies scale and provenance but never states the search domain (federal awards/grants recipients) or search behavior (what query matches against). The sibling us_recipient_search_basic is not named or contrasted.

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 when-to-use or when-not-to-use guidance at all. The description mentions 'Intended future paid tier,' which is pricing metadata, not usage guidance, and actively leaves the agent unclear on whether this tier is appropriate to call now. The obvious alternative (us_recipient_search_basic) is never mentioned.

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