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

Annotations only cover the safety profile (readOnly, idempotent, openWorld). The description adds substantial behavioral context: results are capped at 5 parents, the three columns are never summed or sequential, PAC totals are company-wide and from voluntary contributions, absences are search results rather than facts, and the register's own interpretive disclaimer is quoted.

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?

Purpose is front-loaded in the first clause, but the prose is a dense multi-clause run-on and repeats the 'never added / never a sequence' point three separate times. Much of the caveat text is decision-relevant, yet it could be tightened considerably without loss.

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 no output schema, the description does the work of describing the return structure (up to 5 parents, three side-by-side record types by component/fiscal year, cycle, and year) and what absence means. Given a single required parameter and read-only annotations, it is close to complete; only result-shape precision suffers from being conveyed in prose.

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%, so the baseline is 3, but the description adds real meaning: the substring is matched against the company name, the USAspending parent, the reviewed alias note, and recipient names, and it is scoped to the 100 largest parents. That goes beyond the schema's 'case-insensitive company, parent or recipient name substring'.

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 and resource: 'Look up an ICE or CBP contractor in the Pay-to-Play Register by company name substring', then lists exactly what matching covers and what comes back (up to 5 parents, three federal record columns). It clearly differs in content from pay_to_play_awards/committees/totals, but it never names those siblings or routes the agent to them, so it falls short of a 5.

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?

Usage is implied by 'look up ... by company name substring' and by the scope caveat that a company outside the 100 largest parents is a scope statement. There is no explicit when-to-use/when-not statement and no named alternative among the four pay_to_play* siblings, leaving the choice to inference.

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