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

Annotations cover safety (readOnly, openWorld, non-destructive) but the description adds far more: per-cell coverage states (present/pending/none), exact fiscal-period deck joins, a ±1d single-candidate webcast match, the important caveat that a missing webcast is not evidence no webcast was held, and a not-point-in-time disclaimer pointing at vantage_date tools. This is exactly the behavior an agent needs to avoid over-reading results.

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 concept before examples, and the routing block is scannable. It is dense and longer than typical, with three example phrasings that partially overlap, but essentially every clause carries distinguishing or caveat information.

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?

There is no output schema, yet the description conveys the row shape (artifact cells with present/pending/none states), the joins used, and known data gaps. An agent can call this and correctly interpret the result without further documentation.

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 ticker and limit are already documented including the default of 12 and newest-first ordering. The description's 'one row per fiscal period' framing clarifies what limit counts, but does not add syntax, formatting, or edge-case guidance beyond the schema. Baseline 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 resource with its granularity: a per-fiscal-period document index, one row per quarter/year, aggregating 8-K, transcript, 10-Q/10-K, deck, and webcast. It then explicitly disclaims being a figures tool, which cleanly separates it from get_earnings and get_financials.

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?

Gives three concrete user-phrasings that should route here plus a full negative routing list (numbers → get_earnings, XBRL → get_financials, calendar → get_company_events, slide text → get_ir_documents, call commentary → compare_earnings_calls). Nothing is left to inference about when to select this tool versus a sibling.

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