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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the safety profile is covered. The description goes further by disclosing the cost model ('a few free samples a day, then $0.02 USDC per call via x402'), which is meaningful operational context absent from the structured fields. It stops short of describing pagination or response limits.

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 tight sentences with the field list front-loaded and the input mechanics immediately after; nothing is redundant. The pricing sentence is relevant but slightly vague ('a few free samples a day'), which keeps it from a clean 5.

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?

With an output schema present, return values need not be explained, and the description nonetheless previews the profile contents. It covers the two inputs, the matching behavior, and the payment gate, leaving only minor gaps around parameter precedence and result limits for a read-only, idempotent lookup.

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 100% and both parameters are documented, so baseline is 3. The description adds value by clarifying the resolution behavior — an id is exact while a name is resolved to the 'best match' — semantics the schema does not convey. It does not specify precedence when both are supplied.

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 specific resource (a federal recipient profile) and enumerates its fields (name, UEI, parent, business types, location, totals), so an agent knows exactly what comes back. It does not explicitly contrast this with siblings like us-spending__search or us-spending__award, so it falls short of the 5 bar for sibling differentiation.

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?

'Give id, or name to use the best match' tells the agent both inputs work and that name triggers fuzzy resolution, which is useful invocation guidance. However, it never states when to reach for this tool versus us-spending__search (the obvious upstream step for obtaining an id), leaving the workflow to inference.

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