save_user_note

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

With no annotations, the description carries full burden. It discloses that the note is durable and that it is a new (not update) operation, and adds the 'one sentence' constraint. It does not mention return values, error conditions, or overwrite behavior, but for a simple save operation this is minimal yet sufficient.

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 two short sentences with no wasted words. It front-loads the core purpose and adds a key exclusion and constraint.

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?

For a simple one-parameter save tool with no output schema, the description adequately covers purpose, scope, and a safety note. It omits return behavior, but that is often implicit for save operations. The simplicity of the tool keeps the completeness high.

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 schema only says 'note' is a required string. The description adds semantic meaning: it should be a one-sentence user preference. This compensates for the 0% schema description coverage by providing format guidance.

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 action ('Save'), the object ('a NEW durable user preference'), and explicitly excludes financial data, distinguishing it from the many financial sibling tools. This is a specific verb+resource+scope definition.

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?

'NEW' implies creation rather than listing or deleting, and 'Not financial data' provides an explicit exclusion. However, it does not name alternative tools for listing or deleting notes, so it stops short of full when/when-not guidance.

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