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

Annotations already declare readOnlyHint, openWorldHint, and destructiveHint=false. The description adds genuinely useful behavioral context beyond that: it is deterministic, returns a TRUST/BLOCK verdict, and costs $0.005 USDC on Base. It does not disclose latency, failure modes, or what a BLOCK response contains, but the payment requirement and output semantics are meaningful additions.

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 dense sentences, front-loaded with the core capability and ending with the pricing/logistics detail. Jargon (CanaryGuard, DexScreener) is compact but each phrase carries information; little waste.

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?

With an output schema present, the description needn't explain return values, and with full schema coverage the parameters are documented. It conveys purpose, output verdict type, and cost, leaving only usage routing and edge-case behavior unaddressed for a 4-param security gate.

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 description coverage is 100%, so chain, target_url, strict_mode, and token_or_service_address are already documented in the schema. The description adds no parameter-level meaning (e.g. what strict_mode changes or how target_url influences the verdict), so the baseline 3 applies.

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?

States a specific verb+resource (a pre-trade gate that inspects tokens) and enumerates the concrete capabilities: DexScreener liquidity, Base/Solana RPC honeypot inspection, and CanaryGuard injection scrubbing. It is easy to distinguish from security_url_threat_check or security_evm_calldata_firewall by capability, though it never names a sibling explicitly.

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?

"Pre-trade gate" implies the usage context (run before executing a trade to get a TRUST/BLOCK verdict), so usage is implied rather than stated. There is no explicit when-to-use, when-not, or alternative-tool routing against the many security_* and *_trending_* siblings.

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