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

No annotations provided, so description carries full burden. Discloses payment requirement for indexed addresses (0.01 USDC via x402 on Base) and warns that `unknown` is not to be inferred as safe. Does not explicitly state read-only nature, but sufficiently covers key behavioral traits.

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, front-loaded with purpose and output description. Second sentence adds crucial clarification and payment note. No wasted words.

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?

Without output schema, description adequately explains return format (verdict with sub-scores) and payment condition. Could mention that both parameters are required, but implied. Good overall.

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% (both parameters described). Description mentions payment for 'indexed addresses' but doesn't add significant meaning beyond schema for the two parameters. 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?

Describes a specific verb+resource: 'Pre-transaction health/safety verdict for an onchain app, by contract address.' Clearly differentiates from siblings (get_methodology, get_universe) which are about methodology info and universe listing.

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?

Implied usage as pre-transaction safety check, but no explicit when-not-to-use or alternatives. Clarifies that `unknown` is a real answer, but lacks comparison to siblings or conditions for using other tools.

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