veto_session_save

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

Annotations already indicate it is not read-only and not destructive. The description adds behavioral context: it mentions auto_summarize uses MCP Sampling and session_id prevents session inflation. However, it does not disclose potential side effects, error conditions, or whether the save is synchronous.

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 extremely concise (three sentences) and front-loaded with the primary purpose. Every sentence provides essential information with no fluff, making it efficient for an agent to parse.

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 11 parameters and no output schema, the description covers the main use cases. However, it omits important interplay details (e.g., recommending to omit context/summary/task_state when auto_summarize is true), which are present in the schema but not in the description itself. Still, with high schema coverage, it is mostly complete.

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% with good parameter descriptions. The tool description adds extra meaning for key parameters: auto_summarize and session_id (e.g., 'prevents session inflation when refreshing mid-conversation'). This goes beyond the schema, enhancing agent understanding.

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 core action: 'Saves the current session context to SQLite.' It also highlights two key features: auto_summarize and session_id for updating. However, it does not explicitly differentiate this tool from sibling session tools (e.g., veto_session_replay, veto_sessions_list), which would help an agent choose correctly.

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 provides usage guidance: when to use auto_summarize and when to pass session_id for updates. But it lacks explicit when-not-to-use or alternative tool recommendations. The guidance is implied rather than explicit, leaving some ambiguity.

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