save_note_tool

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

No annotations are provided, so the description carries the disclosure burden. It adds that the note is 'free-form' (arbitrary text accepted) and persists for later recall via the 'remembered' framing, but says nothing about durability, scope, or permissions. For a simple single-field write, this is minimal but not misleading.

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?

A single front-loaded sentence with no wasted words. It is efficient, though its brevity is part of the reason sibling differentiation is absent.

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?

An output schema exists, so return values need not be explained, and there is only one required param. Still, the description omits any differentiation from the four sibling save/remember tools and any privacy or scope context for stored notes.

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 0% — the single 'note' parameter has no description in the schema. The description partially compensates by indicating the value is a free-form note or reminder, but adds no format, length, or content constraints. With only one simple param, baseline is not fully met but the gap is small.

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 states a clear verb ('Save') and resource ('note or reminder') and clarifies the content is free-form. It does not, however, differentiate itself from closely related siblings like save_identity_tool or remember_turn_tool, so an agent must infer the boundary on its own.

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 phrase 'the user wants remembered' implies a trigger condition (explicit user intent to persist something), which is useful. But there is no explicit when-to-use guidance, no conditions for choosing this over remember_turn_tool or save_identity_tool, and no stated exclusions.

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