get_income_statement

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

No annotations are provided, so the description carries full burden. It mentions data source (SEC EDGAR XBRL) and that each period includes a filing date, but lacks details on rate limits, authentication requirements, data latency, or any limitations. For a read-only data tool, more behavioral context is needed.

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 two sentences, free of redundant information, and front-loads the core purpose. Every word adds value.

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 no output schema, the description effectively communicates the data fields included (revenue, cost of revenue, etc.) and the data source. It could be improved by mentioning return format (e.g., JSON structure) but is otherwise complete for a simple retrieval tool.

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%, with both parameters documented in the schema. The description adds context about the data content (e.g., 'standardized income statement') but does not enhance parameter understanding beyond what the schema provides (ticker and period with enum). Baseline 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 a standardized income statement (revenue, cost of revenue, operating income, net income, EPS) for US public companies from SEC EDGAR XBRL filings. It differentiates well from siblings like get_balance_sheet or get_cash_flow.

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 income statement retrieval but provides no explicit guidance on when to use this tool versus alternatives (e.g., when to use quarterly vs annual). No exclusions or prerequisites are mentioned.

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