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

With no annotations provided, the description carries the behavioral burden. It discloses that the operation is append-only, writes to the memory:{id} stream, and leaves the memory body unchanged, which is important context beyond the tool's name. It could add details about duplicate votes or failure behavior, but the output schema covers return shape.

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 compact and front-loaded: the first sentence states the action, and the second paragraph adds only essential behavioral guardrails. There is no filler, redundant schema restatement, or vague introductory language.

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 4-parameter tool with a full output schema and no annotations, the description covers what the tool does, how it behaves, and which sibling tools handle related cases. An agent has enough information to invoke it correctly without guessing about side effects.

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 description coverage is 100%, and each parameter already has a meaningful description: vote is an enum with semantics, memory_id is traced to a prior memory_recall, and note/agent are optional overrides. The description reinforces that memory_id refers to a recalled memory but adds little new parameter-level meaning beyond the schema.

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 opens with 'Record +1/-1 feedback on a recalled memory id', naming a specific action, object, and allowed value range. It also distinguishes itself from nearby memory tools by stating it does not modify the memory body and by pointing corrections and rewrites to memory_remember, memory_forget, and memory_skill_feedback.

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 explicitly tells the agent when this tool is not the right choice: corrections belong on memory_remember/memory_forget, and skill/playbook rewrites belong on memory_skill_feedback. It clearly implies use after a memory_recall hit when the goal is only to record a positive or negative vote.

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