doi_score_verify

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

With no annotations, the description carries full disclosure burden. It reveals that verification is local, the default pubkey is hardcoded, and there is an override mechanism. However, it does not mention return values or failure behavior (e.g., what happens if verification fails), which is a minor gap.

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 only two sentences long, efficient, and front-loaded with the core purpose. Every piece of information earns its place without redundancy or fluff.

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 that there is no output schema, the description does not explain the return value (e.g., boolean, object). However, it adequately covers the tool's operation, parameters, and configuration options. For a verification tool, the missing output specification is a modest 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?

While the input schema already describes both parameters, the description adds value by noting the hardcoded default pubkey and the environment variable override (ORACLE_PUBKEY), which is not in the schema. This enriches understanding beyond the schema's field-level descriptions.

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 uses the specific verb 'verify' and resource 'DoI score envelope', clearly stating the action. It distinguishes itself from siblings doi_score_lookup and doi_sign_vouch by focusing on local verification without network calls.

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 explicitly mentions that no network call is made and that the oracle pubkey can be overridden via parameter or environment variable. It lacks explicit 'when not to use' guidance, but the context is clear enough for typical use cases.

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