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

No annotations exist, so the description carries the full burden and does so well: it discloses that raw hex plus decoded fields are returned, that the exact position is not on-chain (only a commitment), that a ZK range proof is carried, that the region name is an off-chain label, and that comma-separated batchIds are checked against a single contract-state fetch with per-ID found/not-found results.

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?

Front-loaded with the core action and the sibling contrast, and each subsequent sentence adds a distinct, non-redundant fact. It runs long, but no sentence is filler or restates the schema.

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?

With no output schema, the description compensates by describing the return content (raw hex plus decoded fields) and the shape of the multi-ID response. The proof/label caveats close the remaining interpretive gap for an agent.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: batchId accepts several comma-separated IDs processed in one fetch with per-ID found/not-found results, and network support spans preprod and mainnet.

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 a specific verb (verify) and resource (GYOTAK catch record), plus the exact source (Midnight blockchain on-chain state). It explicitly contrasts itself with the sibling get_catch_reports, so an agent can route between the two without opening either 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?

Explicitly names the alternative (get_catch_reports) and the condition that selects this tool instead: trustless verification without trusting GYOTAK. It also notes what the sibling returns (date, district, verify links, never GPS), making the choice concrete.

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