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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false. The description adds genuinely useful behavioral context beyond them: that File C data can be partial or lagged and that these rows do not establish the full award obligation or amount paid. That is a substantive caveat that prevents misreading results.

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?

Front-loads the core purpose, follows with the caveat, and ends with sort-field options. Mostly efficient, though the first sentence and the 'Shows which Treasury accounts...' sentence overlap somewhat.

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-format explanation is unnecessary, and the annotations carry the safety profile. The description supplies the important data-quality caveat; the main remaining gap is parameter meaning for generated_award_id and pagination, which is minor for a read 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%, and the description only clarifies the sort parameter by listing valid sort fields. It leaves the required generated_award_id and the page/limit/order pagination params undocumented, so it only partially compensates for the coverage gap.

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 (Fetch) and resource (File C funding data for an award) and enumerates the data dimensions (federal account, object class, program activity). Clear on its own, but it never distinguishes itself from sibling tools like get_award_funding_rollup or get_award_detail, which an agent must choose between.

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 purpose implies usage (line-item funding sources for a single award), but there is no explicit when-to-use guidance and no mention of alternatives such as get_award_funding_rollup. The agent is left to infer selection from the name and sibling set.

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