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

With no annotations, the description must carry the burden of behavioral disclosure. It correctly implies a read-only operation via 'Retrieve' and 'Access raw financial data', but it does not mention potential limitations, rate limits, pagination, or the exact structure of the response beyond listing revenue, expenses, and net income. This is adequate but not rich.

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 only two sentences and avoids excessive verbosity. The first sentence is slightly redundant by repeating 'As Reported Income Statements API', but overall it is efficient and front-loaded with the core purpose.

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 provides a basic understanding of the tool's output by mentioning revenue, expenses, and net income, but it lacks details on the return format, date ranges, or behavior across multiple periods. Given the absence of an output schema, this is a clear gap, though not fatal.

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 input schema has 100% description coverage for all three parameters (limit, period, symbol). The description adds no additional meaning to the parameters, so the baseline score of 3 is appropriate.

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 clearly states the tool retrieves income statements as reported by the company, using a specific verb ('Retrieve') and resource ('income statements as they were reported'). It also emphasizes raw financial data from official filings, which distinguishes it from sibling tools like getIncomeStatement or getIncomeStatementGrowth.

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 phrase 'as they were reported' and 'raw financial data directly from official company filings' conveys a clear use case: when original, unadjusted data is needed. However, it does not explicitly name alternative tools or state when not to use it, so it falls short of full explicit guidance.

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