Get 10-Year Cash History

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

Beyond the readOnlyHint annotation, the description discloses deduplication logic (annual preferred over quarterly) and chronological sorting. It also mentions the return structure, providing rich 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?

Three concise sentences deliver core functionality, return format, dedup logic, and feature-gating. No fluff or 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?

Given the output schema exists, the description appropriately provides a high-level overview of the output structure. It covers source, range, dedup, and access constraints, making it complete for a simple one-parameter tool.

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%, but the description adds value by stating the ticker must correspond to a company with SEC filings, which conditions the parameter's validity. This goes beyond the schema's generic ticker description.

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 retrieves up to 10 years of quarterly cash position history from SEC XBRL filings, specifying data source, time range, frequency, and output format. It uniquely identifies the tool's purpose among siblings like get_cash_position and get_cash_runway_calendar.

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 states it's not feature-gated and works for any company with SEC filings, providing clear context for when to use it. While it doesn't name exclusions or alternatives, the unique purpose differentiates it from sibling tools.

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