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

Annotations already declare readOnlyHint=true, so the safety profile is covered; the description adds real value beyond that by warning the response contains PII and describing the JSON:API { data } envelope plus the underlying REST route. It does not cover error behavior, but for an annotated read tool this is solid behavioral disclosure.

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 verb/resource/scope, then return shape, then endpoint mapping in a compact span with no filler. The REST route notation is slightly machine-facing but costs little.

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?

No output schema exists, so the description must carry return-value information — and it does, naming the JSON:API shape and the presence of check results and PII. The single parameter is fully documented, leaving only minor gaps such as auth or error semantics.

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% and there is only one parameter, so the schema already documents verification_id fully; the description's 'ver_...' hint duplicates the schema example. Baseline 3 is appropriate since nothing new is added.

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 (verification by id), and scopes it precisely as 'one identity check within an inquiry', then enumerates concrete check types (government-id, selfie, database, document). The parent/child relationship to an inquiry implicitly distinguishes it from persona_get_inquiry, though no sibling is named explicitly.

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 says what it fetches but never states when to call this instead of the sibling getters (persona_get_inquiry, persona_get_report), nor any prerequisite for having a verification id. Usage is only implied by the parameter.

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