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

Annotations only carry readOnlyHint=true, and the description goes well beyond that: it warns that netBuybacks is a derived dilution proxy rather than a buyback figure, that split-basis share counts are withheld rather than shown as phantom buybacks, and that IFRS reporters are refused rather than served zeros. It also discloses the SEC EDGAR XBRL source, a 24h cache, and that caveats ride in tool_notes.

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 and return shape, and every sentence carries distinct information (field list, derived-metric caveat, split handling, refusal behavior, source, tier). It is dense and the inline object listing is heavy, but with no output schema that detail earns its place.

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?

With no output schema, the description carries the return contract itself, enumerating every field as parallel arrays aligned to `years` and explaining the tricky derived metrics. Combined with source, cache, tier, and refusal semantics, an agent has everything needed to call and interpret it correctly.

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 100% for the single ticker parameter, so the schema already documents it fully. The description adds no ticker-specific meaning (format, case, exchange prefixes), so the baseline of 3 applies.

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 purpose ('Where a company sent its cash, up to 30 annual labels') and enumerates the exact returned fields, so the resource is unambiguous. Naming get_fundamentals and get_debt_maturities as complements helps an agent separate this tool's capital-allocation niche from adjacent fundamentals tools.

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 says it 'complements get_fundamentals and get_debt_maturities' and notes a Researcher tier requirement, which implies context but never states explicitly when to choose this over those siblings or when not to call it. No alternative-selection rule is given.

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