getIncomeStatement

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

No annotations are provided, and the description only says 'Retrieve' (implying read-only) and lists filter options. It lacks details on authentication, rate limits, pagination, or response format, leaving significant behavioral gaps for a complex tool.

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 concise sentences with clear front-loading of the primary purpose. Every word adds value, and there is no redundant information.

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?

Despite 12 parameters, no annotations, and no output schema, the description is too brief. It does not explain return format, pagination behavior, filter interactions, or any prerequisites, leaving the agent underinformed for a complex financial report 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%, so parameters are well-documented in the schema. The tool description adds little beyond the schema (e.g., 'per-customer scoping'), but with full schema coverage, the baseline is 3.

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 an income statement (P&L) report and mentions scoping filters (per-customer, per-contract, per-account) and selection options (currency, cadence), distinguishing it from sibling tools like getBalanceSheet.

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 retrieving income statements with various filters but does not explicitly state when to use this tool vs. alternatives (e.g., getBalanceSheet) or any exclusions.

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