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

Annotations already declare idempotentHint and destructiveHint, but the description adds meaningful behavior: the tool is explicitly 'Pull, not push,' it advances state only once the verdict has settled, and it explains why retrying is safe ('asking again is how the answer arrives'). This goes beyond what the annotations alone say.

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 first sentence is strong and front-loaded, but the rest is verbose and grammatically tangled: 'Pull, not push, for the reason RefreshOwnerVerification is...' and 'A tool, like RefreshOwnerVerification beside it, and idempotent for the same reason...' are hard to parse. The final sentence about the verb heuristic is meta-commentary that does not help an agent invoke the tool.

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 low complexity (one parameter, full schema coverage, output schema present, and safety annotations), the description supplies enough context: purpose, usage scenario, push-vs-pull behavior, and idempotency rationale. Minor vagueness in 'moves it on' and the confusing phrasing prevent a perfect score.

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% and the single parameter is documented as a UUID value wrapper. The description does not add any parameter-specific meaning beyond the schema, so the baseline of 3 is appropriate.

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 first sentence states a specific verb and resource: 're-reads the provider's verification verdict for a submitted application and moves it on when the verdict has settled.' This clearly identifies what the tool does and the outcome it produces, and the reference to RefreshOwnerVerification helps an agent distinguish it from a closely named 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 description gives clear situational context: an applicant may be waiting on a state change because 'a webhook nobody received' means the verdict may already be settled. It also frames the tool as a pull operation and idempotent, implying it is safe to retry. It does not explicitly list exclusions or alternative tools, so it stops short of a 5.

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