End Session

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It identifies that the operation ends a session, but it does not disclose side effects, whether an active session is required, whether the action is reversible, or what happens to session data afterward. For a state-changing tool, this is a meaningful gap.

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 short sentences with no filler. The core action and the invocation trigger are both front-loaded and every clause contributes useful 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?

The tool is moderately complex with five parameters, a required summary, and no output schema or annotations. The description plus fully-covered schema give an agent enough to invoke the tool, but important behavioral context—such as prerequisites around an active session and consequences of ending it—is missing.

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 description coverage is 100%, so the schema already documents all five parameters and their meanings. The description reinforces that 'summary' captures what was accomplished and implies 'next_steps' relates to what to do next, adding slight context, but it does not need to compensate for missing schema info.

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 states a specific verb 'End' with a specific resource, 'a work session', and the key content of the operation: summarizing what was accomplished and what to do next. This clearly differentiates the tool from siblings like start_session and get_session_brief.

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 explicitly says 'Call this when the user is done working,' which provides a clear trigger condition for use. It does not name alternatives or explicitly state when not to use it, but the usage context is unambiguous given the sibling set.

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