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

With no annotations, the description carries the burden of behavioral disclosure. It does convey that the data is real-time and scoped to public/private companies and ETFs, but it omits important behaviors such as what the return structure looks like, how 'TTM' is calculated, pagination behavior, or any rate limits. This is minimal but not misleading.

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 concise with two sentences, and the first sentence front-loads the core purpose. The second sentence adds generic use cases but does not include operational specifics; it is somewhat fluffy but not overly verbose.

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?

Given the large set of sibling tools with similar income statement functions, the description is incomplete because it fails to define TTM, contrast with standard or as-reported income statements, or describe the expected response data. The lack of an output schema further increases the need for narrative explanation, which is absent.

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 already provides full descriptions for both parameters (symbol and limit), so schema coverage is 100%. The description adds no extra parameter semantics beyond the schema, and it does not clarify how 'limit' interacts with the TTM data or what range of values might be meaningful. Baseline 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 accesses real-time income statement data for public companies, private companies, and ETFs, which is a specific resource and action. However, it does not explain the 'TTM' (trailing twelve months) aspect or differentiate among the many sibling income statement tools (e.g., getIncomeStatement, getIncomeStatementAsReported).

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 usage for up-to-date profitability tracking, competitor comparison, and business trend analysis, but it offers no explicit guidance on when to choose this tool over the numerous other income statement variants. It does not mention exclusions or alternatives, leaving the selection largely to inference.

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