treasury.monthly-statement

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

No annotations are present, so the description carries the full burden. It discloses that data includes monthly and fiscal-year-to-date totals by classification, but omits behavioral traits like read-only nature, rate limits, pagination behavior, or required permissions. The description is adequate but not fully transparent.

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?

The description is a single, well-structured sentence that front-loads the core identity ('Monthly Treasury Statement (MTS) — Table 4') and efficiently lists the classifications. No extraneous words or redundancies.

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?

Given no output schema, the description covers the data scope (receipt categories, time aggregation) but misses details on response structure, pagination, and parameter usage. It is somewhat complete for a data retrieval tool but leaves gaps for an AI agent to infer.

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%, yet the description does not explain the parameters (sort, fields, filter, pageSize, pageNumber). It only describes the content (receipt classifications) without linking to how parameters affect results. This leaves the agent without meaningful parameter guidance.

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 identifies the tool's purpose: retrieving Monthly Treasury Statement Table 4 federal receipts by source. It lists the classification categories (individual income tax, corporate income tax, etc.), distinguishing it from sibling tools like treasury.cash or treasury.debt that cover different financial data.

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 implies the tool is for federal receipts data but does not explicitly state when to use it versus alternatives. No exclusions or comparative guidance are provided, so the agent must infer usage from context.

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