financial_statements

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description adds context about parsing HTML or PDF and extracting specific tables, but it does not disclose potential limitations like dependency on company listing status, missing data for unlisted companies, or the exact structure of the returned tables.

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 a single, well-structured sentence that front-loads the tool's purpose and output. Every phrase adds value with no repetition or filler.

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?

The description lists the line items that will be extracted, which is helpful, but there is no output schema and no statement about return format or example usage. Given the moderate complexity and lack of parameter guidance, the description is adequate but has noticeable gaps.

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?

The schema has 0% description coverage for the 'context' parameter (the only parameter). The tool description does not explain how to fill the context object, such as the requirement to provide 'company' or the optional fields, leaving the agent to infer from property names alone.

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 uses specific verbs ('Locates' and 'extracts') and names the resource (annual report / financial statement filing) and the structured line-item outputs (revenue, net profit, EBITDA, assets, equity, debt). This clearly distinguishes it from sibling tools like ratio_analysis or company_profile, which address different data.

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 implies the tool is for retrieving raw financial line items from filings, but it does not explicitly state when to use it over alternatives such as ratio_analysis or company_overview. No exclusions or alternative tool references are provided.

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