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

Adds substantial context beyond the readOnly/idempotent annotations: the cumulative year-to-date nature of cash-flow figures, the CSV return format with its column structure, and the candidate-list behavior on ambiguous input. These are non-obvious behavioral traits an agent would otherwise get wrong.

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?

Dense but front-loaded: the core purpose leads, followed by the critical interpretation caveat and the return-format note. Every sentence carries information, though the middle YTD warning is slightly clause-heavy.

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, the description compensates by describing the CSV column layout and the JSON candidate alternative. Combined with the fallback explanation and the statement-type semantics, an agent has everything needed to call and interpret this correctly.

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%, so the baseline is 3, but the description goes further by tying the 'cashflow' enum value to its cumulative interpretation and explaining the ambiguous-symbol candidate flow. It reinforces and clarifies parameter meaning rather than merely repeating it.

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?

States a specific verb and resource ('Get full line-item detail for one financial statement'), names the three statement types, and scopes it to a CSE symbol with one row per line item. This clearly separates it from siblings like get_quotes, get_ohlc_data, or get_market_summary.

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 when to use it — one statement for one symbol, all available quarters — and gives actionable guidance on interpreting cash-flow vs income-statement figures and on the ambiguity fallback. It does not explicitly name alternative tools, so it falls short of a 5.

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