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

With no annotations, the description must carry the burden of behavioral disclosure. It mentions 'as reported' and 'original form', indicating raw data, but does not explain pagination, default behavior, ordering, or potential response size. It provides some context but lacks depth.

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, front-loads the purpose, and includes no filler. It efficiently conveys the tool's function and scope.

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 is moderately complex with no output schema. The description covers the basic data categories but does not describe the return structure, how the three statements are combined, or any prerequisites. It provides sufficient orientation but leaves gaps about expected response format.

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 parameters have schema descriptions (100% coverage), so the baseline is 3. The tool description clarifies the scope of data returned, but adds no additional meaning to limit or period beyond the schema. It doesn't explain how period affects results or how limit applies to multiple statements.

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 comprehensive financial statements with a specific verb ('Retrieve') and resource ('financial statements as reported'). It also lists the included components (income, balance sheet, cash flow), which helps distinguish it from sibling tools focused on single statements, though it doesn't explicitly name them.

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 comprehensive financial data across all three statements but does not explicitly state when to choose this tool over alternatives like getIncomeStatementAsReported or getBalanceSheetStatementAsReported. No exclusions or contrast with siblings are provided.

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