session

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

No annotations are provided, and the description fails to disclose behavioral traits such as side effects, state changes, or authentication requirements. For example, it doesn't clarify if 'prime' modifies session state or if 'handoff' requires multi-device coordination details.

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 reasonably concise with a short introductory sentence and a bulleted list of actions. The initial '[HINT: ...]' adds minor noise but does not significantly detract from structure.

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 the high parameter count (25), zero schema coverage, and no output schema usage, the description is incomplete. It fails to map parameters to actions, provide examples, or explain behavior for the majority of inputs.

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 coverage is 0%, and the description only explains the 'action' parameter by listing its possible values. The remaining 24 parameters (like include_hints, task_id, etc.) are not described, leaving the agent without guidance on their purpose or usage.

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 it's a unified session management tool for actions: prime, handoff, prompts, and assignee. It distinguishes from sibling tools by consolidating multiple session-related functions.

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 lists four specific actions with brief explanations, providing clear context for when to use each. However, it does not explicitly state when not to use this tool or mention alternatives.

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