recall

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

Annotations already mark the tool as readOnlyHint=true and idempotentHint=true, so the description adds only the phrase 'semantic search' to indicate the retrieval method. This is a minor behavioral clarification beyond the annotations, but it does not disclose other aspects like result ordering or pagination.

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 extremely concise: two sentences (19 words) that front-load the primary action and then list filters. No wasted text; 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?

Given the tool's simplicity (6 parameters, no output schema, clear annotations), the description covers the core purpose and key filter options. However, it omits explanation of the 'path' parameter (auto-loading) and the structure of returned results, which would be helpful for complete agent comprehension.

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%, earning a baseline of 3. The description adds value by specifying valid values for the 'time_range' parameter ('today, week, month, all'), which the schema only describes as 'Time filter'. This extra detail aids the agent in constructing correct queries.

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 states 'Retrieve memories using semantic search,' which clearly identifies the verb and resource. However, it does not differentiate from the sibling tool 'search,' which could cause confusion for an agent deciding between them.

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?

No guidance is provided on when to use this tool versus its siblings (e.g., 'search', 'remember', 'index'). There is no mention of context, prerequisites, or exclusions, leaving the agent without direction for appropriate selection.

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