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

Annotations declare readOnlyHint=false and destructiveHint=false, so the bar is lower. The description adds that it checks the proof against its verification key and public inputs, which is useful context beyond the name. However, it does not disclose what side effects occur despite not being read-only (e.g., whether verification records state, consumes the proof, or requires specific permissions), leaving a transparency 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?

Two sentences, zero waste. The purpose is front-loaded in the first sentence, and the second sentence adds precise mechanical detail. Every sentence earns its place without redundancy or extraneous information.

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 one-parameter tool with no output schema, the description covers the core action and what is verified. However, because annotations indicate the operation is not read-only, the description should at least hint at potential side effects or what a successful verification does (e.g., records a result). This gap keeps it from being fully complete, though the simple shape of the tool limits the severity.

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 there is only one parameter, whose schema description already states it is the ID of the ZK proof to verify. The description adds no additional syntax, format, or constraint details beyond what the schema provides, so the baseline 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 verb (Verify) and resource (ZK proof) with the key identifier (proof ID), and the second sentence clarifies the verification mechanism (verification key and public inputs). It does not explicitly differentiate from siblings like verify_bounty or pcc_oracle_verify, but the ZK-proof resource is distinct enough that an agent can identify the tool without opening the schema.

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?

No when-to-use guidance, prerequisites, or alternatives are provided. The description only states what the tool does, leaving the agent to infer when to select this tool over other verification-related siblings. There is no mention of when not to use it or what conditions make it appropriate.

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