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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior, but the description adds substantial context beyond that: what rows are returned, which labels appear side by side, that COPS/JAG/forfeiture figures are never summed, and critical interpretation caveats about absence from published lists and lack of scoring/payout data. These are exactly the behavioral nuances an agent needs.

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?

The description is front-loaded with the core action and dataset scope, then layers in return contents and necessary caveats. It is somewhat dense and long, but nearly every sentence (non-additivity, absence interpretation, scoring/payout disclaimers) carries real information rather than filler.

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?

There is no output schema, so the description does a good job explaining what is returned and the limits of the data. It covers absent data and non-additive figures, though it could be slightly more explicit about result structure or pagination behavior for a list-returning 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?

The schema already fully documents the single 'recipient' parameter, including its case-insensitive substring semantics and 80-character limit. The description restates 'by name substring' but adds no new parameter-level meaning beyond the schema, so the baseline 3 is appropriate.

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?

States a specific verb (Find), resource (institutional recipients), and precise dataset scope (Police Grant Register's DOJ COPS award lists, FY2020 to latest). It also distinguishes the content from related datasets by naming what is included (award rows, DOJ-list/ICE 287(g) labels, equitable-sharing payments) and what is not (COPS/JAG/forfeiture additions).

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?

The description implies usage via 'by name substring' and clarifies the scope of the COPS lists, but it does not explicitly say when to use this tool versus siblings such as police_grant_awards, sanctuary_doj_list, or forfeiture_payments. No exclusions or alternative-selection guidance are provided.

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