Register and check provider claims: signed statements, methodology, evidence, and an explicit self-reported vs signature

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

Annotations already declare non-readonly, non-idempotent, open-world, non-destructive. The description adds genuinely useful non-annotation context: it costs $1.00 via x402 on eip155:8453 and maps to POST /v1/bio/trust/providers. It does not say what happens on repeat registration (relevant given idempotentHint=false) or what 'self-reported vs signature-verified' means operationally.

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 compact sentences with the core purpose front-loaded. The pricing/route parenthetical is dense but earns its place by disclosing the paid call. No filler.

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?

An output schema exists so return values need not be explained, but for a paid, non-idempotent mutation tool with 8 undocumented parameters and no usage routing, the description leaves too much unspecified — especially the action/mode semantics and parameter intent.

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 0% across 8 parameters, so the description must carry the burden. It only loosely gestures at claims/signed_statement/evidence concepts and says nothing about action, status, filters, provider_id, name, or service_versions, leaving most parameters semantically undefined.

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 names a specific verb pair and resource ('Register and check provider claims') plus the concrete artifacts involved (signed statements, methodology, evidence, self-reported vs signature-verified). It is clearly a bio/trust-provider tool and distinguishable from neighbours like v1_bio_provenance_verify or v1_bureau_reputation, though the dual register/check mode is never tied to the 'action' parameter.

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?

There is no statement of when to use this tool rather than the many adjacent trust/verification siblings, and no indication of which action values select 'register' vs 'check'. The only routing information given is a transport/price detail, not usage guidance.

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