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

The annotations only declare readOnlyHint and openWorldHint, while the description adds important behavior: pricing at $0.005 per result, a signed artifact with expiry and a public verification key, and scope limitations such as proving HirePulse issuance but not ownership or purchase safety. There is no contradiction with the 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 compact and front-loaded with the artifact definition and its key limitation. Every sentence adds useful information: provenance, price, usage routing, and exclusion.

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?

Given the output schema, annotations, and full schema coverage, the description supplies the remaining decision-critical details: cost, what the badge proves and does not prove, and when to choose sibling tools. An agent has enough information to select and invoke this tool correctly.

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%, and both parameters are already well documented in the input schema. The description does not add parameter-level semantics beyond what the schema provides, so the baseline score of 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?

The description states a specific artifact and resource: a signed public-evidence statement for a merchant domain, including expiry and a public verification key. It also explicitly distinguishes this from pre_purchase_merchant_trust_check and x402_merchant_trust_check, and clarifies what the badge proves versus what it does not prove.

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?

It gives explicit when-to-use guidance ('Use when you need a portable signed assessment') and names two alternatives with their selecting conditions: pre_purchase_merchant_trust_check for risk evidence without a badge, and x402_merchant_trust_check for an API endpoint. It also states an exclusion: it does not issue a third-party certification.

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