getBalanceSheetStatementTTM

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint, so the safety profile is covered structurally. The description adds no behavioral context of its own: nothing about period coverage of TTM figures, whether values are annualized/averaged, freshness of data, or how the limit behaves. The second sentence is marketing framing, not behavior.

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?

Two short sentences with no bloat, but the space is spent on generic marketing ("gain insights into a company's financial health") rather than the one fact that matters, the TTM qualifier. Front-loading is weak because the distinguishing information is absent entirely.

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?

There is no output schema, so the description must carry the burden of explaining what comes back, and it does not — no mention of period fields, statement structure, or how TTM figures are computed. Combined with the missing TTM explanation and no sibling differentiation, the definition is under-specified for a tool whose name is its main source of meaning.

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 100%, documenting symbol and limit (default 100, max 1000), so the baseline is 3. The description does not restate or enrich either parameter, and notably says nothing about what one result row represents, which matters for the limit parameter.

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 verb and resource ("Access detailed balance sheet statements"), so the general domain is clear. But it never mentions the TTM (trailing twelve months) qualifier that distinguishes this tool from siblings getBalanceSheetStatement and getBalanceSheetStatementGrowth, so an agent cannot tell from the description which of the three it wants.

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 when-to-use guidance and no mention of alternatives, even though the sibling list contains near-identical tools (getBalanceSheetStatement, getBalanceSheetStatementGrowth, getBalanceSheetStatementsBulk). The only stated context is "publicly traded companies," which every sibling shares.

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