Save conversation turn

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

No annotations provided, but description discloses the operation's purpose and warns against storing secrets. However, it lacks details on overwrite behavior, content size limits, or error responses, which would enhance transparency.

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?

Four sentences, all essential. Front-loaded with purpose, then usage guidelines, then parameters. No wasted words.

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 is adequate for a simple write tool with no output schema. It explains the context (Orchestrator continuity) and constraints. Missing details on success/error feedback, but given the tool's simplicity, it's nearly 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 covers all parameters with descriptions. The description adds context about using a stable session_id and ensuring content has secrets removed, which goes beyond schema. High schema coverage means baseline 3, so 4 reflects 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 tool saves a turn from various roles into UnClick conversation history, with a specific verb and resource. It distinguishes itself from siblings by tying to Orchestrator continuity and being the primary receipt path.

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?

Explicitly specifies when to use (after accepted human turn and assistant reply when client can call tools), and provides fallback instructions if unavailable. Also advises using stable session_id and avoiding secrets.

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