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

Annotations already declare readOnly/no-destructive, so the description's real contribution is the non-obvious fiscal_year defaulting behavior and the caveat about sparse data right after October 1. It also notes the response always carries fiscal_year back, which is behavior not derivable from annotations.

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-loaded with the core purpose, then the return shape, then the fiscal_year caveat. Every sentence adds something, though the parenthetical about USAspending's internal default is slightly more detail than needed.

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-value explanation is not owed, and the fiscal_year trap is well covered. But for a paginated, sortable, 6-parameter tool with zero schema descriptions, the description leaves paging/sorting and the required agency code unexplained.

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 6 parameters, and the description only explains fiscal_year. toptier_code (the sole required parameter), page, limit, sort, and order receive no semantic explanation anywhere, leaving the agent to guess formats and paging behavior.

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 with scope: list the Treasury Account Symbols (federal accounts) used by an agency. It does not, however, differentiate itself from close siblings like list_federal_accounts or get_federal_account_detail, so the agent must infer the distinction.

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 understanding how an agency's money flows through Treasury" implies the use case but gives no explicit when-to-use/when-not rule and never names an alternative for e.g. cross-agency or single-account lookups, which the sibling list makes highly relevant.

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