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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description then adds genuinely non-obvious behavior: fiscal_year defaults to the last *completed* fiscal year rather than the current one, with the rationale (USAspending returns only a few days of data right after October 1), and guarantees that the response always carries fiscal_year. That is real value beyond the structured fields.

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?

Three short paragraphs, front-loaded with the definition, then the practical framing, then the fiscal_year caveat. Little filler; the example and the October 1 rationale both earn their space, though the parenthetical gloss on 'program activities' partially repeats the first sentence.

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 and the description correctly notes the fiscal_year field is always returned, so return values need no further explanation. However, for a paginated, sortable list tool whose only required input is undocumented, the description leaves meaningful gaps around the toptier_code identifier and pagination semantics.

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% across six parameters, so the description must carry the burden, but it only explains fiscal_year. The required toptier_code is never defined (format, where to obtain it, relationship to list_toptier_agencies), and page/limit/sort/order and the two sort enums are left entirely to the bare schema titles.

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 ('List the program activities ... within an agency') and reinforces it with a concrete example ('Cybersecurity and Infrastructure Security Agency') plus a scope note that these are the named programs that obligate funds. It does not explicitly distinguish itself from the close sibling get_federal_account_program_activities, so an agent must infer agency-level vs federal-account-level from the name alone.

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?

'Useful for pinpointing which program funds a specific activity' gives one concrete use case, and the fiscal_year paragraph implicitly tells the agent not to assume current-year data. But there is no guidance on when to prefer this over get_agency_overview, get_agency_object_classes, or get_federal_account_program_activities, and no prerequisites or exclusions.

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