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

The description adds meaningful behavioral context beyond annotations: it discloses the cost ($0.002 USDC via x402), the free first cached result, and clarifies the output is market context only, not a recommendation. These are not in the annotations (which already cover readOnly/idempotent/destructive hints), so the description provides added value.

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 and front-loaded: the first sentence states the core purpose, the second adds critical context (not a pick) and cost details. Every sentence earns its place with zero redundancy.

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 tool with one optional parameter and no output schema, the description covers the core purpose, cost, and non-recommendation stance. It does not describe the result format or what 'social-intelligence' entails, but given the simplicity and that the payment flow is already in the schema, it is nearly complete.

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 sole parameter (x_payment) is fully described in the schema (100% coverage), including the challenge-retry flow. The tool description itself does not add parameter-level detail, but since the schema already carries the full meaning, the baseline of 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 clear purpose: scanning quality-screened Base tokens with social-intelligence and trusted-KOL context. It uses a specific verb ('Scan') and resource ('Base tokens'), and adds a clarifying note that it is market context only, not a pick or recommendation. However, it does not explicitly differentiate from sibling tools like otto_rh_season or other scan tools, so it stops short of 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 gives no guidance on when to use this tool versus alternatives. It implies a use case (scanning Base tokens with social context) but does not state exclusions or mention sibling tools. Given the large sibling list, this is a significant gap.

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