retrieve_memory

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

With no annotations, description takes full burden. States side effect: 'Reads from the semantic memory store built by build_memory,' clarifying it's a read-only operation and identifying dependency. No mention of auth or rate limits, but the simple read nature reduces concern.

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?

Four sentences with no redundant text. Main purpose announced first, followed by usage guidance, side effects, and prerequisite. Every sentence adds value.

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?

Given presence of output schema and simple search tool behavior, description adequately covers purpose, usage, and side effects. Does not detail return format but output schema handles that. Lacks mention of pagination or timeouts, but not critical for this tool.

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 has 100% coverage, so baseline is 3. Description adds context that query uses natural language and embedding is handled, providing some value beyond schema. However, it does not add critical new information for each parameter.

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 'Semantic search over stored memories' with specific verb and resource. Differentiates from sibling tools by focusing on semantic retrieval of similar workflows and patterns, which is distinct from creating tasks or listing events.

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 clear usage context: 'Use this to discover relevant past work when facing a new task.' Also gives a prerequisite: 'Use build_memory first to ensure the index is up-to-date.' Does not explicitly state when not to use or name alternatives, but the context is sufficient.

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