getIncomeStatement

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

With no annotations, the description must fully disclose behavior. It only states the tool returns quarterly income statements, but lacks details on data freshness, format, pagination, rate limits, or whether it covers all industries comprehensively. This is minimal transparency.

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 sentence that is concise and front-loaded. It avoids verbosity but could be slightly more structured (e.g., specifying the output format or scope). Still, it efficiently conveys 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?

Given the tool's simplicity (no parameters, no output schema) and many siblings, the description leaves gaps. It does not explain the return structure, period boundaries, or data coverage limitations. The agent may need additional context to use it correctly.

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 is empty, so schema coverage is 100%. The description does not add parameter information because none exists. The baseline is high since no parameters need explanation, and the description does not mislead.

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 quarterly income statements for all listed companies in general industry. It uses a specific verb ('Get') and resource ('quarterly income statements'), and the scope is defined. Among sibling tools like getBalanceSheet, getIndustryEPS, and getProfitAnalysis, this tool is clearly distinguished.

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?

No guidance is provided on when to use this tool versus siblings, nor any context about prerequisites, date ranges, or limitations. The agent has no information about when not to use it or what alternatives exist.

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