upvote_memory

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

The description explains the effect (boosts ranking) but does not disclose whether upvotes are reversible, if there are limits, or what the response contains. With no annotations, more detail would improve 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?

The description is very concise with no wasted words. It clearly states the purpose, usage condition, and effect in a compact format.

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 covers the essential aspects: purpose, usage condition, effect, and parameter source. It omits details about the response, but the tool is simple. Output schema exists but description doesn't reference it.

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 description instructs the agent to use the memory ID from recall output, which is crucial context not present in the schema. This guides proper invocation.

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 specific verb-resource pairing 'upvote memory', clearly states the purpose (boosting ranking), and implicitly distinguishes from siblings like downvote_memory by focusing on helpfulness.

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 provides explicit guidance on when to use: when a recalled memory helped solve a problem. It does not cover when not to use or suggest alternatives, but the context is straightforward.

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