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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, giving the agent a strong safety profile. The description adds that it returns 'reported financial statements' (implying historical/actual data rather than projections) and supports quarterly/annual periods. However, it doesn't disclose output volume limits beyond the schema 'limit' param or describe pagination/response format 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?

The description is a single efficient sentence that communicates the core purpose. It's appropriately concise without wasted words, though it could slightly expand on scope or usage guidance without becoming verbose.

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 tool has an output schema present and full schema parameter coverage, so much of the context is handled structurally. The description covers the core intent (financial statements by period). However, given the existence of many market_* sibling tools, it could better situate itself—e.g., noting it reports fundamental/accounting data as opposed to market prices or analyst views, which 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 description coverage is 100%, so the schema already documents all three parameters (symbol, period, limit) with descriptions and enums. The description doesn't add meaningful semantics beyond what's already in the schema. Baseline 3 is appropriate since the schema carries the burden well.

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: 'Return reported financial statements, ratios, and metrics for one company by quarterly or annual period.' It clearly specifies what is returned and the periodicity. It's a solid purpose statement, though it could better distinguish itself from siblings like market_company_profile or market_earnings.

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 provides no guidance on when to use this tool versus alternatives like market_quote, market_earnings, or market_price_history. It doesn't mention prerequisites, whether ratings/analyst data is included (which market_analyst_ratings handles), or how it relates to its siblings. No when/when-not guidance given.

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