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

Annotations provide readOnly, openWorld, idempotent hints. The description adds valuable behavioral context: the tool is free, lists specific anomaly categories, and mentions on-chain references on Base. It does not contradict annotations and provides warnings about usage.

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 extremely concise yet packs detailed information: anomaly types, on-chain references, and usage advice. Every sentence carries value without unnecessary 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?

For a tool with no output schema, the description adequately explains the nature of returned data (anomalies with on-chain references) and lists examples. However, it could be more explicit about the format (e.g., list of objects) for full completeness.

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 coverage is 100% for the single parameter (days). The description does not add extra semantic meaning beyond the schema's description of the look-back window, so a score 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 title and description clearly specify the tool's purpose: listing live x402 security incidents (anomalies) with on-chain references. It distinguishes itself from sibling tools by listing specific anomaly types and emphasizing it's measurements, not accusations.

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 usage guidance ('Check before paying anything') but does not explicitly state when to use this tool versus alternatives like check_x402_endpoint or mcp_security_report. It lacks explicit when-not or exclusion clauses.

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