advance_stage

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

The description discloses the primary behavior (advancing cursor), the failure mode (clean with directive), and resultant action (pointing to finalize_session). No annotations exist, so description carries full burden and does so adequately.

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 sentences with no wasted words: first states purpose, second covers failure behavior. Front-loaded with key action.

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 simple tool with one parameter and an output schema, the description covers main behavior and edge case. Could briefly explain 'directive payload' but not essential.

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 0% with no descriptions for session_id. The description does not elaborate on the parameter beyond its name, missing an opportunity to add meaning for the required input.

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: 'Advance the session's stage cursor to the next stage in its expected_stages.' It differentiates from siblings like finalize_session by specifying stage advancement rather than session termination.

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 implies usage when progressing through expected stages and provides guidance when the session is at its final stage by directing to finalize_session. However, it does not explicitly state when not to use this tool versus other sibling tools.

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