x402 Trust verified providers

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

With no annotations, the description carries the full burden. It usefully defines what 'verified' means (domain control plus confirmed contact email) and discloses a real behavioral trait — verification is informational and never affects the score — but says nothing about read-only safety, permissions, or result shape.

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 tight sentences with no filler, and the identifying criteria are front-loaded. The opening is a noun fragment rather than a verb phrase, a minor structural weakness, but overall efficient.

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?

For a simple read-only list tool with full schema coverage this is adequate, and pagination is covered by the schema. However, with no output schema the description doesn't indicate what fields a listed provider contains, leaving a small completeness gap.

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 both limit and offset are already fully documented with ranges and defaults. The description adds no parameter context, which is acceptable at this coverage level but earns no credit above baseline.

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 clearly identifies the resource (hosts that proved domain control and confirmed a contact email) and implies a listing operation. It implicitly differentiates itself from score-related siblings via 'it never changes the score', though it never explicitly names an alternative tool.

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?

Usage is implied rather than stated: an agent can infer you call this to see which providers are verified. There is no explicit when-to-use, when-not, or reference to a sibling like x402_trust_score as the alternative, leaving routing to inference.

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