veto_session_restore

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

Annotations show 'readOnlyHint: false' and 'destructiveHint: false', indicating a non-destructive write. The description's 'restores' aligns with this, implying state mutation without destruction. No contradictions.

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-sentence description with the main purpose first, followed by ancillary guidance. Every sentence adds value; no redundancy or fluff.

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?

No output schema is defined, but the tool's purpose (restore session) is well-covered. Could optionally mention return value (e.g., success indication), but not essential for agent use.

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 100%, so baseline is 3. The description mentions 'by ID' for session_id but adds no detail about 'resuming_as' beyond schema. Minimal added value.

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 the action 'restores' and the resource 'saved context snapshot of a previous session', explicitly differentiating from the sibling tool 'veto_session_replay' by contrasting 'working context' vs 'chronological event timeline'.

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?

Provides explicit guidance to use 'veto_sessions_list' to find session IDs and names an alternative tool ('veto_session_replay') for a different use case. Lacks explicit 'when not to use' but context is clear.

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