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

With annotations already declaring readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, the description adds valuable behavioral context beyond them: the payment model ('first eligible cached intelligence result is free; otherwise calls cost $0.003 USDC through x402'), the x402 challenge flow, and the nature of the output ('guarded AI summary'). This goes beyond the safety profile covered by annotations.

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 sentences, each earning its place: the first states purpose and content, the second scopes the tool and differentiates it, and the third explains the payment mechanism. Information is front-loaded and there is no fluff.

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?

Despite no output schema, the description adequately tells an agent what data to expect (trends, margins, EPS, leverage, recent filings, AI summary) and how to handle payment (x402 challenge). For a read-only tool with only two parameters, nothing essential is missing for correct invocation.

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 both parameters (ticker, x_payment) are already thoroughly documented in the schema. The tool description does not add param-level semantics beyond implicitly referencing output fields, so the baseline 3 applies.

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 the verb ('Read') and specific resource ('SEC-EDGAR fundamentals and filings context for a US ticker'), and lists exact data points (revenue, net-income trends, margins, EPS, leverage, filings). It explicitly differentiates from other tools with 'Fundamentals scanner only; not a price feed or recommendation,' which helps an agent distinguish it from siblings like otto_equity_smart_money.

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 gives clear context for when to use it (when SEC-EDGAR fundamentals are needed) and includes an explicit exclusion ('not a price feed or recommendation'). However, it does not name alternative sibling tools directly, so the guidance is strong but not fully explicit about routing to specific alternatives.

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