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

Annotations only declare openWorldHint=false and destructiveHint=false, so the description carries the burden for behavioral disclosure. It does reveal that the tool triggers a state transition (hands to review) and describes an auto-verification to the video-call booking step. However, it does not disclose edge cases (e.g., what happens if documents are missing or passport is illegible) or idempotency, so the disclosure is partial but not contradictory.

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 concise sentences, front-loaded with the primary purpose, followed by a specific caveat. No wasted words; every sentence earns its place.

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?

For a single-parameter tool with an output schema (so return values need not be described), the description adequately covers the core action and precondition. It is slightly incomplete in not clarifying the behavior when documents are missing or if the passport is illegible, but these are secondary details given the output schema exists.

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% because the sole parameter (applicationId) is described as 'UUID value wrapper,' which is minimal. The description adds no further meaning about what applicationId represents or how to obtain it. Per the baseline for high coverage, this stays at 3 without additional context.

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 action ('hands the case to the provider's review team') with a clear precondition ('once identity documents are on file') and an optional fast-track for legible passports. This clearly distinguishes it from itin_submit_itin_intake (which submits the intake) and other itin_* tools.

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?

It gives a clear context for when to use the tool ('once identity documents are on file') and even describes the autoverification path for passports. However, it does not explicitly name alternatives or when not to use it, though the sibling names make the distinction inferable.

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