usa_spending_over_time

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

The annotation readOnlyHint already tells the agent this is a safe read operation. The description adds no behavioral details beyond that, such as rate limits, response format, or any side effects.

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 short sentences that are front-loaded with the core action. Every word is necessary and there is no fluff.

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?

The description covers the main purpose but does not mention the multiple optional filters (agency, state, keyword) or response structure. Given 7 parameters and no output schema, more guidance would improve completeness.

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%, so baseline is 3. The description does not elaborate on parameters; it only mentions time grouping options. It adds no extra meaning beyond the schema.

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 the verb 'Get' and resource 'federal spending aggregated by time period'. It implicitly distinguishes from siblings like usa_spending_by_agency, usa_spending_by_award, etc., by focusing on time-based aggregation.

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 indicates use for time-based aggregation and trend identification, but does not explicitly state when to avoid this tool or name alternatives. The distinction from siblings is clear from context.

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