get_income_statement_12_month_report

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

With no annotations, the description carries the full burden. It only says 'Generates a 12-month income statement report' with no mention of side effects, read-only nature, authentication needs, or processing time. For a reporting tool, it likely has no side effects, but that is not disclosed.

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, front-loaded sentence, which is concise. However, it is too brief for the tool's complexity, but from a pure conciseness standpoint it is not 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?

The tool has 9 parameters, including nested objects and filtering options, and no output schema. The description does not explain how the 12-month report works (e.g., trailing 12 months, calendar year), what the output contains, or how parameters like 'columns' affect the result. It is incomplete for a complex report generator.

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?

All 9 parameters have descriptions in the input schema (100% coverage), so the baseline is 3. The description adds no additional meaning beyond what the schema provides, neither clarifying nor extending parameter semantics.

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 generates a 12-month income statement report. However, it does not distinguish from the sibling get_income_statement_date_range_report, which also generates an income statement for a date range. The '12-month' qualifier is specific but not explained.

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 alternatives like get_income_statement_date_range_report. There is no mention of the 12-month constraint or context for its use. The agent is left to infer usage from the name alone.

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