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

With no annotations, the description carries the burden of behavioral disclosure. It reveals key defaults (quarterly, last 4 periods) and the efficiency of one round-trip. However, it does not disclose the output structure, potential large payload, error handling, or any limitations regarding data completeness for the three statements. This is a moderate disclosure level.

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-loaded with the primary function and defaults, and the second sentence provides usage context. Every sentence adds value without redundancy or irrelevant details. It is exemplary in conciseness.

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 the absence of an output schema and annotations, the description should ideally explain the return structure or any caveats. It covers the core purpose, defaults, and usage, but does not describe what the combined response looks like (e.g., how the three statements are organized) or any edge cases. This leaves the agent with some uncertainty about the output 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?

The description adds meaning to 'period' and 'limit' by stating 'default quarterly, last 4 periods,' which directly explains the default behavior of these two parameters. However, it does not elaborate on the range of 'limit' or the full enum of 'period' beyond the default, and 'ticker' is only implied. Schema coverage is low, so the description partially compensates but not fully.

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's function: it returns all three financial statements (income, balance sheet, cash flow) for a ticker in a single round-trip. It also specifies the default quarterly frequency and last 4 periods. The phrase 'instead of three separate statement calls' explicitly distinguishes it from sibling tools that provide individual statements.

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 explicit when-to-use guidance: 'Call this when the user wants a full fundamental picture of a company instead of three separate statement calls.' This clearly differentiates it from individual statement tools. However, it does not explicitly state when not to use it (e.g., if only one statement is needed), leaving that to implication.

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