get_cashflow_statement

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

No annotations exist, so the description must carry behavioral disclosure. It indicates a read-only historical operation, but fails to mention response format, how limit and period affect returned data, or any other runtime behavior. This is thin 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?

One clean sentence, front-loaded with the core action and no filler. It's appropriately concise for a three-parameter tool, though it could have gained a fifth point by briefly noting limit/period semantics.

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?

An output schema exists, so return documentation is not needed, and sibling context helps disambiguate. But with no parameter documentation and no annotations, the agent must guess at limit and period semantics. The definition is minimally adequate, not fully complete.

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 description coverage is 0%, so the description needs to compensate for parameter meaning. It implicitly covers ticker but says nothing about limit or period beyond the schema's enum values. An agent cannot fully infer what limit controls or what 'ttm' means from the given text.

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 uses a specific verb-resource pair ('Get historical cash flow statements') and names the target ('public company ticker'). It distinguishes the financial statement type from siblings like get_income_statement and get_balance_sheet, though it doesn't explicitly contrast 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 when historical cash flow data is needed for a public company, and sibling names clarify the domain. However, it offers no explicit when-to-use versus alternatives, no exclusions, and no guidance on choosing annual, quarterly, or ttm periods.

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