treasury_monthly_statement

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

Describes keyless nature, default date range, and detailed behavior of excludeSummaryRows with server-side filter. Annotations (readOnlyHint, openWorldHint) are consistent and description adds significant behavioral context.

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?

Single paragraph packed with essential information, front-loaded with purpose. Every sentence adds value without redundancy.

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?

Covers return fields, parameter defaults, and critical behavioral nuance. No output schema, but the description sufficiently explains what the tool returns.

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 coverage is 100%, and description adds meaning: explains default startDate, clarifies excludeSummaryRows effect and server-side filter. No parameters lack clarity.

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 description clearly states it provides federal receipts, outlays, and deficit/surplus by month from the MTS table 1. It specifies return fields and distinguishes itself from siblings by being the highest-value budget-analysis tool.

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 description explicitly labels it as 'highest-value budget-analysis tool,' guiding usage. It does not explicitly list when not to use or alternatives, but the context of sibling tools implies its specific domain.

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