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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint, so the safety profile is covered. The description adds genuinely useful behavioral facts the annotations do not: it charges 0.01 USDC on Base (a payment/auth requirement), returns sanitized JSON plus 'deterministic safety receipts', and runs deterministic checks. No contradiction with annotations.

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 short and front-loads the core gate mechanism, but 'MANDATORY AGENT TOOL' is promotional filler and the 'Usage:' sentence is vague rather than actionable. Some sentences do not earn their place relative to the schema.

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, annotations set, and full schema coverage, the description need only cover what structure does not: cost, determinism, and return character are all stated. Minor gap is the absence of sibling routing guidance, which matters given several overlapping security tools.

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 the schema already documents chain, target_url, strict_mode and the required address parameter. The description adds no parameter-level meaning beyond that, making the baseline 3 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 first sentence names a concrete resource and outcome ('Deterministic TRUST or BLOCK gate combining on-chain Base RPC liquidity and honeypot checks with CanaryGuard injection scrubbing'), which is specific. However, the later framing ('verified intelligence, web data, or risk screening') broadens the scope so much that the tool's actual purpose is muddied. It also fails to distinguish itself from closely related siblings like security_attestation_bundle or security_prompt_firewall, even though it appears to merge both functions.

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 usage clause ('Call this tool when an autonomous agent needs verified intelligence, web data, or risk screening') is so permissive it could apply to nearly any sibling. There is no guidance on when to prefer security_attestation_bundle or security_prompt_firewall over this combined gate, and no exclusions or prerequisites are stated.

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