start_identity_verification

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

No annotations are provided, so the description carries full responsibility. It discloses that the tool creates a session (mutation) and returns a session ID. It also explains the required next steps. However, it omits details like session expiration, idempotency, or error handling, which keeps it from maximum transparency.

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 extremely concise: three sentences covering action, output, and workflow. It is front-loaded and contains no unnecessary words or redundancy.

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 no output schema, the description adequately explains the return value (session ID). It integrates well with sibling tools in the workflow. However, it could be more complete by mentioning prerequisites (e.g., user must be provisioned) or error cases, though the schema partially covers the user_id requirement.

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%, so baseline is 3. The description adds no additional information about parameters beyond what the schema already provides (e.g., purpose, user_id, provider). There is no extra guidance on parameter values or constraints.

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 creates an identity verification session using Incode SDK and returns a session ID. It distinguishes itself from sibling tools like get_identity_verification and submit_identity_verification by specifying its role as the first step in a multi-step workflow.

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 explicitly outlines the correct workflow: use this tool first, then follow up with get_identity_verification and submit_identity_verification. This provides clear when-to-use guidance and names specific sibling tools for subsequent steps.

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