Manage Sessions

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

Annotations already indicate readOnlyHint=false (mutation) and destructiveHint=false (not destructive). The description adds the notion of sensitive actions like 'start' and 'end' but does not disclose side effects, reversibility, or what happens to session data on end. It introduces 'context snapshot' and 'next tasks' for bootstrap, which is a helpful behavioral detail, but lacks depth about state changes or consequences.

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 compact sentences with zero filler. The purpose is front-loaded, and the action list is provided efficiently in parentheses. Every word earns its place, making it easy to scan.

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?

With 8 parameters, multiple actions, and no output schema, the description is under-specified. It does not explain which parameters apply to which action (e.g., session_id for end, limit for list), nor does it describe the return shape or outcomes. The absence of output schema amplifies the gap, leaving an agent without enough context to call the tool correctly across different actions.

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 baseline is 3. The description does not add any parameter-specific meaning beyond the schema; it only lists action names without mapping them to required parameters. An agent must rely solely on the schema to know which fields matter for each action, which the description does not clarify.

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 a specific verb + resource: 'Manage agent tracking sessions and multi-turn workflow attribution.' It also enumerates four concrete actions (start, end, list, bootstrap), which differentiates it from sibling tools like manage_nodes or manage_tasks. An agent can immediately understand the tool's role without opening the schema.

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 usage by stating its purpose and actions, but does not explicitly say when to use this tool versus alternatives. No exclusions or comparisons are provided. For example, it doesn't mention that tasks would be managed elsewhere, or when a session must be started before tracking. The guidance is implicit rather than explicit.

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