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

readOnlyHint=true already covers the safety profile, but the description adds real value beyond annotations: it discloses that the response contains check results and PII (a sensitivity warning an agent should have), gives the response envelope (JSON:API { data }), and maps to the underlying REST endpoint GET /verifications/{verification_id}. It stops short of any error, auth, or rate-limit behavior.

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 sentences: the first front-loads what is fetched and what the entity means, the second states the return shape and REST mapping. No filler words and nothing redundant.

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 naming the return shape ({ data } with check results and PII), so an agent knows what comes back. Given a single required string param and readOnly annotations, nothing essential is missing — only error/miss behavior is unaddressed.

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?

Only one parameter and schema description coverage is 100%, so the schema already documents verification_id as a string with the ver_... prefix example. The description confirms lookup 'by id' but adds no format, constraint, or validation meaning beyond the schema; baseline 3 applies.

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 (Get) and resource (a single verification by id), and goes further by defining what a verification is — 'one identity check within an inquiry' with concrete examples (government-id, selfie, database, document). This clearly separates it from the list_* siblings, though it does not explicitly name any sibling.

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 phrase 'one identity check within an inquiry' implies the retrieval happens after an inquiry exists, but there is no explicit when-to-use statement, no when-not-to-use, and no pointer to an alternative among the many persona_get_* siblings.

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