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

With no annotations, the description carries the transparency burden. It discloses cost ('There is a cost per session'), return behavior ('return a URL'), and follow-up action ('direct the customer to that URL'). Missing details include failure modes, ownership requirements, or what happens for already-verified wallets.

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 somewhat repetitive—'Creates a new session for Identity Verification' and 'Creates a session for Identity Verification' appear twice, and the link-generation warning is also repeated. While it is organized with param docs, the redundancy could be trimmed without losing information.

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 an output schema exists (not shown but implied), the description adequately covers purpose, prerequisites, parameter semantics, cost, and post-verification callback behavior. It lacks explicit error scenarios or idempotency, but overall it provides sufficient context for an agent to invoke the tool correctly.

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?

The description provides comprehensive parameter documentation despite 0% schema coverage. It explains each param (@param), defines 'profile' values (FULL vs LITE), and details the callback's required format ('must call /callback/didit with the verificationSessionId and status'). This far exceeds the bare schema.

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 clearly states the tool's function: 'Creates a new session for Identity Verification (KYC)' with a specific scope ('only required on wallet that have not been KYC verified'). It distinguishes from check tools like wallet_kyc_check by focusing on session creation, though it does not explicitly name siblings.

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?

Provides explicit when-to-use guidance: 'only required on wallet that have not been KYC verified'. Also includes an important operational instruction: 'Do not generate a link unless explicitly asked for by the user'. However, it does not explicitly reference alternative tools or scenarios where another tool would be preferable.

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