Start Session

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

The annotations already indicate this is a mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds that the session is 'tracked' and captures identity/metadata, but does not disclose side effects such as whether starting a session ends the previous one or how session state is managed.

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?

The description is a single, front-loaded sentence with no filler. It conveys the core action efficiently, earning a high score.

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 its simplicity and full schema coverage, the description is adequate but minimal. It does not explain what 'tracked' means in practice, whether a session must exist first, or what the result of starting one is; for a state-changing tool with no output schema, this leaves some gaps.

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?

The input schema provides full coverage with descriptions for all three optional parameters (project, agent_id, metadata). The description's mention of 'agent identity and metadata' maps to two parameters but adds no additional detail beyond the schema, and 'project' is not addressed.

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 uses the specific verb 'start' with the resource 'new tracked session' and clarifies it captures 'agent identity and metadata.' However, it does not explicitly differentiate from sibling session tools like bootstrap_session or end_session, so it is clear but not distinguishing.

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?

No guidance is provided on when to use this tool versus alternatives. The description simply states what it does without mentioning prerequisites, exclusions, or alternative tools, leaving the agent to infer usage context.

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