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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds valuable behavioral context: the cost structure ('first eligible cached intelligence result is free; otherwise calls cost $0.003 USDC through x402') and the 'Filing scanner only' caveat. This goes beyond the annotations and informs the agent about payment requirements and data scope.

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?

Two sentences with no fluff. The first sentence front-loads the purpose and data fields; the second adds the caveat and cost. Every clause earns its place, and the structure is scannable for an agent.

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 specifies the output data (purchase/sale counts, dollar values, roles, net P/S balance) despite the absence of an output schema. It also covers payment and the 'filing scanner' nature. It omits error handling or edge cases, but for a read-only tool with well-documented parameters, the essential information is present.

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?

The input schema covers both parameters with clear descriptions (ticker format and x_payment purpose/flow). Since schema_description_coverage is 100%, the baseline is 3. The description adds only marginal context about the cost tied to x_payment, but does not clarify parameter usage further, so a 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 states a specific verb ('Read') and resource ('parsed SEC Form 4 insider transactions') and enumerates the data fields (purchase/sale counts, dollar values, roles, net P/S balance). It clearly distinguishes itself from sibling tools like otto_equity_intel or otto_equity_smart_money, which cover different equity intelligence, leaving no ambiguity about what this tool does.

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 notes 'Filing scanner only; not a recommendation,' which gives some context on what the tool is not (a recommendation), but it does not explicitly name alternatives or provide when-to-use vs. when-not-to-use guidance. The purpose is clear enough that an agent could infer usage, but explicit routing to siblings is absent.

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