memo_offload

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

Annotations (idempotentHint=true, destructiveHint=false) are complemented by description details: content-addressed storage, deterministic synopsis, exclusion from recall hook, and return fields. Adds significant context beyond annotations.

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?

Description is concise (three sentences) and front-loaded with the main action. Could be better structured (e.g., bullet points for return fields are already in text). No wasted words.

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?

Covers purpose, return format, deduplication, recall behavior, and retrieval. Missing explanation of 'title' parameter and error conditions, but overall comprehensive for a storage tool with good annotations.

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 0% and description does not explain the 'title' parameter (optional, default null). Only 'content' is implicitly described as the bulky payload. Agent left to infer title's purpose.

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?

Clearly states 'Offload a bulky payload... out of the context window' with specific verb and resource. Distinguishes from siblings by noting that offloaded blobs are excluded from auto-recall and can be fetched later with memo_get(id).

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?

Provides explicit context for usage ('bulky payload') and suggests alternative (memo_get(id) for retrieval). Lacks explicit when-not-to-use or exclusions, but sufficient for typical scenarios.

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