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

Annotations already establish readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered; the description adds genuinely new behavioral facts: every value carries filing/form/tag provenance, missing facts return null rather than 0, and each call costs $0.25 after a trial. It does not explain the shape of the returned payload (which statements, how many periods), which is a moderate gap given no output schema.

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?

Three short sentences, front-loaded with the resource and source, then the provenance/null guarantee, then price. Nothing is padding and the cost note is placed where an agent will see it before invoking.

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?

For a single-parameter, read-only lookup with no output schema, the description covers source, data guarantees, and cost. It falls short only on return structure (which statements or periods are included) and ticker format, both of which the agent would otherwise have to discover by calling.

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?

There is one parameter and schema description coverage is 0%, so the description has to compensate. It clarifies that the ticker must be a US-listed symbol and that it maps to SEC EDGAR filings, but it never states the expected format (e.g. "AAPL" vs "NASDAQ:AAPL") or handling of delisted/ticker-changed symbols.

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 specific verb (extract) and resource (verified financial statements and derived metrics) plus the exact source boundary: US-listed tickers, SEC EDGAR XBRL filings. That source detail is enough to separate it from siblings like company_report or validate_financials without opening either schema.

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?

Usage is implied by the source restriction (US-listed tickers), so an agent can infer when the tool applies, but there is no explicit when-to-use guidance and no statement of when to prefer a sibling such as company_report or validate_financials. The agent must reason from the surrounding toolset.

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