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

Annotations already declare idempotentHint=true and destructiveHint=false, and the description reinforces idempotency while adding useful context: it does not start a verification and does not carry personal data. This goes beyond the structured annotations without contradicting them.

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?

The description is two tight sentences with no wasted words. The core action is front-loaded, and the idempotency and privacy constraints are stated clearly and briefly.

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?

Given the simple two-parameter shape, existing output schema, and annotations covering idempotency and safety, the description is largely complete. It could explicitly state that a verification must already exist, but 'Does not start a verification' effectively conveys that prerequisite.

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%, so the baseline is 3. The description maps applicationId and ownerId to 'banking application' and 'beneficial owner' in prose, which adds some semantic clarity beyond the terse 'UUID value wrapper' schema text, but it does not add substantial parameter-level detail.

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 ('re-reads') and a specific resource ('identity-verification outcome for one beneficial owner on a banking application'). It also narrows scope to a single owner and explicitly says it does not start a verification, distinguishing it from related refresh tools like banking_refresh_application_provider_status.

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 makes clear that this tool refreshes and records an existing verification outcome, and the 'Does not start a verification' clause is a useful when-not signal. It lacks an explicit alternative recommendation, but the context is clear enough that an agent can infer when it applies.

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