note

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

The readOnlyHint=false annotation already signals a write operation, and the description's 'Save' is consistent with that. However, it does not disclose important behavior such as slot conflict handling, idempotency/replay semantics, sharing implications, or what happens when the named slot already exists.

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 filler and is front-loaded with the core action. The second sentence adds a useful parameter hint, so every sentence earns its place.

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?

Although an output schema exists and return values need not be described, the input schema is complex with 10 parameters and nested option objects. The description is far too sparse to prepare an agent to call the tool correctly, especially for slot revisions, sharing, reminders, applicability, and relation fields.

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?

With 10 parameters and only 10% schema description coverage, the description is expected to compensate. It only explains the optional slot parameter as naming the current record for a project purpose, leaving initiative, body, kind, name, options, related, sharing, reminder, applicability, and request_id undocumented in the description.

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 a clear verb, 'Save', and names the record types the tool handles: observation, decision, constraint, plan, or outcome. It does not differentiate the tool from siblings such as task_update, context, or reflect, so it falls short of the top score despite being understandable.

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?

It states what can be saved but gives no guidance on when to choose this tool over alternatives, no prerequisites, and no exclusions. An agent must infer usage from the name and description alone.

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