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

With no annotations provided, the description carries the full behavioral burden and does so: it defines the exact decision vocabulary (no_flags/flagged/unknown), states that no_flags never means 'safe', and commits to fail-closed semantics where any unfinished check forces 'unknown'. It also discloses latency, signed results, and payment/rate-limit mechanics.

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?

Front-loaded with the core contract (one call, action+target in, one decision out) before drilling into action-specific rules and pricing. The middle is dense with stacked parentheticals, which costs a little readability, but every sentence carries distinct information.

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?

No output schema exists, yet the description fully specifies the return shape (single decision, merged reasons, per-check results, latency). It also covers pricing, the 5-free-calls-per-day shared limit, and points to verify_result for signature validation, leaving no material gap for a 4-parameter tool.

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%, but the description goes well beyond the terse enum descriptions by giving per-action target semantics (wallet address vs x402 URL for pay, URL/hostname for open, ecosystem plus name@version for install, CVE or 'vendor product version' for patch, agent URL/domain for trust_agent) and notes chain defaults to base for wallet pay.

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 and resource: takes an action+target and runs all relevant PG1 checks in parallel, returning one merged decision. It explicitly positions itself against the sibling single-check tools by promising 'every relevant check' in 'ONE call before an agent acts'.

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?

Clearly frames the use context (a preflight decision before an agent acts) and details which action values are supported and what target each expects. It does not, however, explicitly tell the agent when to prefer it over the granular sibling checks (check_wallet_sanctions, check_package, etc.) or when a single-purpose check is enough.

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