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

Annotations already establish a safe, read-only, open-world read. The description adds genuine value beyond them by disclosing the exact data scope and one real limitation (no discretionary/mandatory breakdown), which saves the agent a wasted call. It stops short of noting history limits or pagination, so not a 5.

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?

Two tight sentences: the action first, the payload second, the limitation last. No filler and nothing buried.

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?

An output schema exists so return values need only be sketched, and the description does that accurately while flagging an in-scope gap. For a one-parameter read tool this is nearly sufficient; only the meaning and source of the agency code is left unresolved.

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% for the single parameter toptier_code, so the description bears the burden and provides nothing — it never explains that "toptier_code" is the agency identifier obtainable from list_toptier_agencies. The phrase "by fiscal year" could also mislead an agent into looking for a fiscal-year argument, which does not exist.

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 sentence gives a specific verb and resource ("Get an agency's budgetary resources") and the second sentence enumerates exactly what comes back (resources, obligations, outlays per fiscal year, plus government-wide figures). It is clearly distinct from siblings like get_agency_overview or get_agency_federal_accounts, though it never names a sibling to route against.

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 note that the endpoint does not provide a discretionary-versus-mandatory breakdown is a useful negative scope hint, but there is no explicit "use this when" statement and no alternative tool named (e.g., a tool that does offer the breakout). Usage is implied rather than guided.

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