income_statements

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

No annotations are provided, so the description must disclose behavior itself. It only states 'Individual pay statements' without indicating read-only nature, result format, pagination, or any side effects. This is essentially no behavioral transparency, failing the minimal disclosure expected for an unannotated 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 extremely short, but it is under-specified rather than concise. It lacks a verb and clear scope, making the brevity ineffective. Every sentence should earn its place; this one states the obvious but not enough.

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?

With no output schema, no annotations, and only two optional parameters, the description still leaves critical ambiguities: what constitutes a 'pay statement', whether results are aggregated, and what the response looks like. An agent cannot fully determine the tool's behavior from this description.

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 coverage is 100%: both parameters (start and end) have clear descriptions (ISO date, inclusive, defaults). The tool description adds no extra meaning beyond the schema, so the baseline score of 3 applies despite the thin description.

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 names the resource ('pay statements') and a timeframe ('in a window'), but it omits a clear verb (e.g., 'list', 'retrieve') and does not distinguish from sibling tools like income_summary. The phrase 'in a window' is vague without specifying the range semantics beyond what the parameters imply.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any conditions, exclusions, or scenarios where another tool (e.g., income_summary) would be more appropriate, leaving the agent to guess.

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