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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), yet the description still adds substantive interpretive constraints: appropriated/obligated/outlaid are separate stages and are never summed, obligations are orders placed rather than outlays, 'probable' law lines are never counted as the law's money, and every answer carries a question note and caption warning against causal reading. That is genuine context beyond the annotations; it loses a point only because it never states result shape or size 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?

The purpose and scoping defaults are front-loaded in the first clause, which is good. But the body is a long semicolon-chained run-on cataloguing data content, making it harder to parse than it needs to be; some of that catalog buys clarity only because no output schema exists.

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 must carry the return contract, and it does: it enumerates the funding/awarding/bridge views, the concentration shares, the P.L. 119-21 wall-system stages with their own as-of dates, the program-activity law lines, and the eight headlines. Combined with fully documented params, an agent has enough to call it and interpret the result.

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 100% and both parameters are enums with documented values, so the schema does the work. The description restates the same defaults (component default both, fy both when omitted) without adding format or interaction detail, which is the baseline case.

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 opening clause names a specific resource (ICE and CBP contract obligation totals from the Pay-to-Play Register) and the two axes it aggregates over (component, fiscal year), so the agent knows exactly what comes back. It does not, however, name the sibling it is not (pay_to_play_awards or pay_to_play_contractor), so differentiation from the other pay_to_play tools must be inferred.

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?

Defaults are stated clearly (both when fy is omitted, both for component), which is real usage guidance. But there is no when-to-use / when-not guidance and no routing to the sibling award-level or contractor-level tools, so an agent must guess whether this or pay_to_play_awards is the right call for a given question.

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