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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive, so the safety profile is covered. The description adds that records are verifier-signed and enumerates the fields they carry (command, environment, checks, limits, standing, notary stamp), which is useful, but it says nothing about pagination behavior despite limit/cursor params.

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?

One dense but well front-loaded sentence that leads with the action and resource, then the addressing modes, then record contents. Compact with no filler, though the compression makes it slightly terse.

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 documented, and the description covers the addressing model adequately for a lookup tool. Minor gap: no note on pagination or how listing results are bounded.

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 high (83%), so the baseline is 3. The description goes further by clarifying how the parameters combine — id addresses one record, while repo with commit, or file, selects a listing — adding meaning beyond the individual field 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?

States a specific verb (read) and resource (verification records, /v/ID) and spells out the two lookup modes: id reads a single record, repo/commit or file lists the newest. It does not explicitly contrast itself with neighbors like notary_get or read_work, so it stops short of a 5.

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?

Gives clear mode selection: use id for a single verification, use repo (with optional commit) or file to list the newest matching records. This is real when-to-use guidance, but offers no exclusions or named alternatives for choosing between siblings.

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