session_boot

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

With no annotations, the description is the sole source of behavioral info. It describes actions (loading, health snapshot, heartbeat) but does not disclose side effects, idempotency, auth needs, or what happens if called multiple times. Adequate but not fully transparent.

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 well-structured sentences, front-loaded with action verbs. Every sentence provides essential information without redundancy. Highly concise and efficient.

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 the tool's complexity (13 parameters, no output schema), the description explains what the tool does but omits what it returns. There is no mention of output format or behavior, which is a gap for an initialization tool. Adequate but not fully complete.

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 does not add extra meaning beyond the schema for any parameter. For example, 'body' is described in schema as 'Recipient body name' and the description only mentions it indirectly. No added value.

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 it initializes a demo session, loads identity/workflow/status from memory, runs a health snapshot, and records a heartbeat. It specifies the tool is for use at the start of a new conversation, distinguishing it from siblings like session_close and health_check.

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?

Explicitly says 'Call this once at the start of every new conversation', providing clear when-to-use guidance. Lacks explicit when-not-to-use or alternatives, but the context of siblings implies when to use other tools.

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