start_session

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

Describes starting a session and returning a session ID, but lacks details on side effects like whether it ends existing sessions or requires a clean state. No annotations provided to compensate.

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?

Docstring format with clear Args and Returns sections. First sentence states purpose immediately. No redundant 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 all necessary parameters and return value for starting a session. Could mention potential conflicts (e.g., only one active session), but overall sufficient given the tool's role.

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 0% schema description coverage, the Arg section adds meaningful descriptions for each parameter, explaining their roles. However, it lacks details on format constraints or expected content.

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?

Clearly states 'Start a new TDD session', giving a specific verb and resource. Differentiates from sibling tools like end_session, pause_session, and resume_session.

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 this tool is used to initiate a session, but it doesn't explicitly state when to use it or when not to, nor does it mention alternatives. Usage is clear by context but not explicit.

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