saveSession

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the basic save action without mentioning potential side effects such as overwriting existing files, required permissions, or the file format used. This is a notable gap for a mutation tool.

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 a single sentence with no redundant wording. Every word contributes directly to understanding the tool's function, making it concise and well-structured.

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 simple functionality and single parameter, the description is minimally adequate. However, the absence of annotations and output schema means the description should have provided more behavioral context, such as return behavior or file-handling details, to be fully 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?

The input schema provides a clear description for the only parameter (filename: 'The name to save the session under'), giving 100% schema coverage. The tool description itself adds no further semantic detail beyond what the schema already conveys, matching the baseline of 3.

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 uses the specific verb 'Saves' and clearly states the resource ('current Prolog session') and the outcome ('to a file for later loading'). It distinguishes from the sibling loadSession by its save semantics, making the purpose unambiguous.

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 for persisting a session for later loading, but it does not explicitly state when to prefer this tool over alternatives or list any exclusions. The phrase 'for later loading' hints at pairing with loadSession but provides no explicit comparison.

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