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

Despite no annotations, the description discloses ordering ('newest first'), provenance ('upstream XBRL tag'), and handling of unreported metrics ('list of metrics this filer never reported'). It also mentions pricing. This is ample behavioral context for a read-only data 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?

The description is a single long sentence with many clauses, including an extraneous pricing pointer at the end. Although informative, it is less concise than it could be; it could be split into shorter sentences. It is not structured with bullets.

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 the returned record structure, metric list, ordering, traceability to XBRL, and unreported metrics, which is substantial given no output schema. It also includes usage context. It is missing explicit error handling or examples, but overall is quite complete for a retrieval tool.

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 descriptions cover all parameters fully (100% coverage). The description adds little beyond naming some metrics, but the schema already explains ticker, period, limit, and metrics with defaults and constraints. Thus the description provides marginal additional semantic value, so score baseline 3.

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 'normalized financial statement view for one company across recent fiscal periods' and enumerates the metrics and derived ratios included. It explicitly contrasts with 'the history of one figure,' distinguishing it from the get_concept sibling.

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 explicitly instructs: 'Reach for this by default when a question is about a company's performance, profitability or margins over annual or quarterly periods rather than the history of one figure.' This provides clear when-to-use guidance and references an alternative type of tool.

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