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

Annotations already declare read-only, open-world, non-destructive access, but the description adds substantial behavioral context: figures are management's own non-GAAP-adjacent characterization, each figure may carry a deep-link and verbatim quote, absence of a receipt is not evidence of error, and point-in-time behavior is explained including how revised releases arrive as new accessions. This goes well beyond what annotations provide.

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 front-loaded with the core identity and return contents, then moves through distinctions, use cases, caveats, and exactness. It is long but appropriately detailed for a complex tool with no output schema; however, some point-in-time detail overlaps with the schema's vantage_date description, keeping it just short of maximally concise.

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-value burden and does so thoroughly: it names the income statement and cash-flow fields returned, explains that figures may include deep-links and verbatim quotes, warns that the table abbreviates values, and points to `<raw_data>` for exact figures. Combined with its caveats and timing context, an agent has everything needed to call and interpret the tool 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%, so the baseline is 3. The description adds meaning beyond the schema by clarifying that `quarters` walks back from `vantage_date` rather than from today, and that vantage_date bounds which releases are visible rather than which extraction is served. This is useful parameter interaction detail not fully captured in 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 states a specific resource (8-K earnings-release financials), enumerates the exact headline figures and cash-flow items returned, and explicitly distinguishes itself from get_financials and get_company_overview. An agent can immediately tell what this tool produces and when it differs from siblings.

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?

It gives explicit use cases with examples and names the alternative tools, explaining that get_financials serves audited XBRL filings while get_company_overview's earnings section is prose without figures. It also states the key timing advantage: this is often the only structured source for fresh quarter capex/OCF/FCF before the 10-Q lands.

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