create_session

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention any prerequisites, side effects, or relationship with other session tools like get_current_session or record_edit, only stating its purpose. This leaves the agent unaware of what creation entails beyond the name.

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 two sentences, with the first sentence stating the primary action and the second giving a use case. There is no redundant information, and it is front-loaded with the core purpose.

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 tool is simple with two optional parameters and no output schema, so the description only needs to convey the core purpose and context. It does that, though it omits details about return values and how the session connects to other editing tools. For a straightforward creation tool, this is adequate.

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 schema already covers both parameters (name and description) with their own descriptions, so the description adds no additional parameter semantics. Baseline 3 is appropriate since schema coverage is 100%, and the description's purpose statement implicitly relates to the session's identity but does not elaborate.

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 'Create a new editing session to group related changes,' which is a specific verb and resource. It distinguishes itself from siblings like get_current_session or create_file_snapshot by referring to an 'editing session' rather than a retrieval or snapshot operation.

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 notes it is 'Useful for organizing different features or experiments,' providing a clear context for when to use it. However, it does not explicitly mention alternatives or when not to use it, such as when you need file snapshots instead.

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