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

With no annotations, the description carries the full behavioral burden and does so well. It discloses that only reviewed events have passages, that absent passages mean unreviewed rather than no events, and that quotes are whitespace-normalized while financial histories are not reconciled. These caveats materially affect how an agent should interpret 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?

Three sentences, front-loaded with the core function and followed by essential caveats. Every sentence adds value and there is no filler or redundant restating of schema 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?

For a one-parameter read tool with no output schema, this description adequately explains the returned data by naming passage types and attached metadata, and it gives explicit rules for interpreting missing and inconsistent data. An agent can correctly anticipate behavior and handle empty responses appropriately.

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%: the single parameter ticker is already documented as 'US ticker symbol, e.g. AAPL'. The description adds no new parameter-level semantics, so the baseline score 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?

The description opens with the specific verb 'Read' and names the exact resource: short, verified primary-source passages for reviewed company events. It enumerates the included attributes (source URLs, section labels, dates, hashes, predecessor links), which clearly distinguishes it from siblings like get_fundamentals and get_company_research.

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 provides useful interpretive context, especially 'no passages means unreviewed, not no events', which tells an agent how to treat empty results. However, it never explicitly states when to prefer this tool over get_company_research or other siblings, nor does it give exclusion conditions. Usage guidance is implied rather than explicit.

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