Verify a researcher, institution, publication or company against public registries, and screen a name against the offici

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

Adds real context beyond the annotations: the call is paid ($0.75), billed via x402/USDC on eip155:8453, and the remote route is given. Annotations cover the safety profile (openWorld, non-idempotent, non-destructive), so the cost and payment disclosure is the valuable addition; it does not, however, warn about repeat charges on retry despite idempotentHint=false.

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 lines with the core purpose front-loaded. The price appears in the title, the first line, and the route line, which is mild redundancy but not bloat.

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 no explanation, and the payment/route detail is present. What is missing for a 5-parameter, zero-coverage-schema tool is any explanation of the request parameters, which is the main 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 0% across 5 parameters, so the description carries the full burden and mostly fails it. It never explains what `check` accepts, the structure of the `query` object, the meaning of `purpose` or `min_score`, or the role of `limit`; only `min_score` is faintly implied by the screening framing.

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 specific verbs (verify, screen) and resources (researcher, institution, publication, company, sanctions lists) so the purpose is unambiguous. It does not differentiate from adjacent bio tools such as v1_bio_provenance_verify, v1_bio_trust_providers or v1_bio_risk_assess, leaving overlap for the agent to resolve.

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 description gives no when-to-use guidance, no prerequisites, and no alternatives — in a sibling set of 100+ tools with several bio-verification neighbours, that omission matters. Only the sanctions-screening half hints at a use case.

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