Begin Verified Continuity Session

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

Since no annotations are provided, the description carries the full burden. It implies a stateful, mutating operation by using 'Begin', but it does not disclose side effects, creation of resources, required verifier/workspace context, or the nature of the portable handle. The description adds minimal behavioral context beyond the core action.

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 a single, succinct sentence with no filler. It immediately states the action and the expected output, making it easy to parse and free of unnecessary detail.

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 tool with 16 parameters, no annotations, no output schema, and a complex domain (session lifecycle), the description is severely incomplete. It does not explain what constitutes a canonical session, what a portable handle is, how the operation relates to sibling tools, or any verification/continuation logic.

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?

With schema description coverage at 0% and 16 parameters (11 required), the description provides no parameter information whatsoever. The agent receives no help understanding what parameters like task_envelope_v1, required_verifier_id, or workspace_root mean, nor how they relate to starting a session.

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 action ('Begin') and the resource ('canonical SDK AgentSession'), and specifies that a portable handle is returned. While it doesn't explicitly differentiate from sibling session tools like aionis_session_resume, the verb 'Begin' strongly implies starting a new session, distinguishing it from resume/continue operations.

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?

No guidance is provided on when to use this tool versus alternatives such as aionis_session_resume or aionis_session_turn. The word 'canonical' hints at a standard entry point, but there is no explicit context, prerequisites, or exclusions.

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