veto_session_save

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

The description explains the tool's behavior in detail: it writes to SQLite, can update in-place, uses MCP Sampling for auto-summarization, resolves context windows per model. Annotations are minimal, so description carries the full behavioral disclosure burden and does so excellently.

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 information-dense yet concise. It is front-loaded with the core action, followed by a warning, then parameter guidance. Every sentence adds value; no 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?

The description thoroughly covers the tool's purpose, triggers, and parameters. However, it does not mention return values or success/failure behavior, which is a minor gap given the lack of an output schema. Still, the description is largely complete for a save operation.

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%, but the description adds significant meaning beyond the schema. For example, auto_summarize is explained with its automatic generation logic, session_id with its update/insert logic, and model with context window resolution. Each parameter gets additional context that aids correct 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 the tool 'saves the current session context to SQLite' and specifies triggers (user typing specific commands). It distinguishes itself by warning against manual DB writes, setting clear boundaries.

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 tells when to call the tool (on specific user commands) and when not to (never write manual INSERT). It provides detailed guidance on using auto_summarize and session_id, making usage unambiguous.

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