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

The annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false. On top of that, the description adds valuable non-obvious behavior: the first eligible cached result is free, otherwise calls cost $0.006 USDC through x402, and this is scanner context rather than investment advice. It does not contradict the 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?

The description is concise: three sentences that front-load the primary action and data scope before covering context and pricing. Every sentence contributes useful information, though the phrase 'Scanner context only' is somewhat redundant with 'not a pick or recommendation' in the same sentence.

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 read-only tool with rich annotations, two well-described parameters, and a clear data scope, this is largely complete. It also covers the payment/caching flow and clarifies that the result is informational. There is no output schema, and the description does not explain the shape of the returned SEC bundle, but the stated selector and contents give an agent enough to decide to invoke it.

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%, and both parameters already have descriptive meanings in the schema: ticker is a US-listed stock ticker, and x_payment is a signed x402 payment payload with challenge-and-retry behavior. The description adds general context about SEC bundle contents and cost, but it does not materially deepen the parameter semantics beyond what the schema provides. Baseline 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 uses a specific verb and resource: 'Read a public-domain SEC bundle for a US ticker' and specifies the contents: 'Form 4 insider activity plus trailing-twelve-month XBRL fundamentals.' This makes the core purpose clear. However, it does not explicitly distinguish itself from sibling tools like otto_insider_trades or otto_equity_smart_money_brief, so it misses the sibling-differentiation that would earn a 5.

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 the tool: when a scanner-style view of Form 4 activity and TTM fundamentals for a US ticker is needed. It also adds a restriction: 'Scanner context only; not a pick or recommendation.' But it gives no explicit when-not-to-use guidance or references to alternative tools, leaving the routing logic mostly inferential.

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