start_session

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

Discloses registration, session start, and pinning. With no annotations, more details on side effects (e.g., session duration, idempotency) would improve transparency. Not misleading but lacks depth.

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: first states purpose, second gives usage guidance. No wasted words, front-loaded with key information.

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?

Covers main purpose and usage but lacks parameter descriptions and return value hints. Adequate for a simple tool, but incomplete due to missing parameter semantics.

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?

Only the 'actor' parameter is contextualized in the description; 'name', 'type', and 'email' are left unexplained. Schema coverage is low (25%), but description only partially compensates.

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 registers an actor and starts a session, pinning the server to that identity. It distinguishes from siblings like claim or commit by being about session management, not content 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?

Explicitly provides when to use (register actor and start session) and when not to (if sharing server, skip and pass actor per call). Offers an alternative approach.

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