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

With no annotations provided, the description carries the full burden of behavioral disclosure. It covers payment behavior (paid $0.02 via x402, challenge response without payment), data sources (GoPlus, honeypot.is), output format (0-100 risk score with reasons), and the non-advisory nature. It also explains x_payment's role. Missing are edge-case behaviors like error handling, but critical behaviors are transparent.

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 dense but well-structured, front-loading the payment aspect ('PAID $0.02') and then explaining functionality and output. Each sentence earns its place, covering payment, data sources, output, disclaimer, and free alternative without redundancy. Slightly long, but justified for a paid tool with these nuances.

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 explains the output's nature (0-100 score with reasons) and lists covered checks (honeypot, tax, ownership, etc.). It covers payment mechanics, data sources, and the free alternative. The supported chains are in the schema, so the description's 'multi-chain' claim is sufficient. Missing details like error scenarios, but overall the context is adequate 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?

The input schema already provides 100% coverage for all parameters, describing chain, address, and x_payment in detail. The tool description reinforces the x_payment flow ('pass x_payment to settle') but does not add substantial meaning beyond the schema's explicit explanation. It provides context about the payment currency (USDC on Base) but does not enrich parameter semantics significantly.

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 tool's function: a multi-chain token honeypot/rug check aggregating GoPlus and honeypot.is data into a normalized 0-100 risk score with explainable reasons. It explicitly names the free alternative token_safety_free, distinguishing this paid version. The disclaimer 'Descriptive facts only — NOT a buy/sell signal' further clarifies its purpose.

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 explains the payment flow: 'Without payment returns the x402 challenge; pass x_payment to settle.' It also points to the free teaser token_safety_free, implying a lighter alternative. However, it does not explicitly state when to prefer this tool over the free sibling, though the paid nature and naming make this inferable.

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