start_session

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

No annotations are provided, so the description must carry the full burden. It discloses loading saved state and recording embodiment, but it does not mention whether starting a session overwrites an existing session, requires an active project, or what side effects occur. This is a significant gap for a stateful operation.

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?

Three concise sentences front-load the main action, with each parameter explained in a separate clause. No unnecessary words.

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?

The description covers the core function, parameter defaults, and optional behavior. However, it omits prerequisite conditions and return values, which would be helpful for a session-starting tool with no output schema.

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%, so the baseline is 3. The description mostly paraphrases the schema: 'Uses current project if project is not specified' mirrors the project parameter description. It adds little additional meaning beyond the 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: 'Start a session and load saved state.' It distinguishes from siblings like save_session and end_session by focusing on initiation and restoration. The first sentence uses a specific verb and resource.

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 provides context on when to use parameters: 'Uses current project if project is not specified' and 'Specify author to restore a specific context-author/role partition.' This gives clear guidance on default behavior and when to specify author, but doesn't explicitly compare with alternatives like get_setup_status.

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