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

Annotations cover the safety profile (readOnly/openWorld/non-destructive), and the description adds substantial behavior beyond them: per-cell honesty states (present/pending/none), exact fiscal-period deck joins, ±1d webcast matching, and the caveat that a missing webcast is not 'no webcast held' when the calendar isn't harvested. It also flags non-point-in-time semantics and points to vantage_date tools for as-of queries.

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 definition, then usage, then routing. Dense but nearly every clause carries operational meaning. Slightly verbose in its emphasis-heavy formatting (CAPS, arrow notation), which is stylistic rather than wasted, keeping it just short of a 5.

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?

No output schema, so the description carries the return-shape burden—and it does, explaining that rows are per fiscal period and what each artifact cell contains and how coverage gaps are represented. Combined with the routing and point-in-time caveat, an agent has everything needed to call and interpret it.

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% and both parameters are documented in the schema itself (limit's range/default, ticker's format). The description adds no syntax or format detail beyond the schema, so the baseline 3 is appropriate—the schema is doing the heavy lifting.

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 verb+resource ('per-fiscal-period earnings DOCUMENT INDEX — one row per quarter/year') and enumerates exactly what each row holds (8-K, transcript, 10-Q/10-K, deck, webcast). It self-describes as a 'navigation index, not figures,' which separates it from data siblings without ambiguity.

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?

Provides three concrete user questions it answers and explicitly routes competing needs to named siblings: numbers→get_earnings, audited statements→get_financials, IR calendar→get_company_events, deck text→get_ir_documents, call content→compare_earnings_calls. When-to-use and when-to-use-something-else are both explicit.

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