getFinancialRatiosTTM

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

Annotations already declare readOnlyHint and idempotentHint, so safety is covered. The description adds context about the types of ratios (profitability, liquidity, efficiency), enhancing behavioral understanding without contradiction.

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 sentences, but the first is slightly redundant ('TTM Ratios API' and 'TTM financial ratios'). Could be more tightly written, but overall efficient.

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 description covers purpose and high-level metric categories, but lacks specific ratio names or output structure. With no output schema, additional detail would improve completeness.

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 has 100% coverage for the single symbol parameter. The description adds no further meaning beyond the schema's 'Stock symbol' description. Baseline of 3 is appropriate.

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 it provides trailing twelve-month financial ratios, specifying categories like profitability, liquidity, and efficiency. It uses a specific verb and resource, and effectively distinguishes from sibling tools like getRatios or getKeyMetricsTTM.

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 (when TTM ratios are needed), but provides no explicit guidance on when not to use or alternatives. It does not mention other ratio tools that may serve different intervals or scopes.

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