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

Annotations already cover read-only and non-destructive behavior. The description adds a prerequisite (needs a workspace/key for durable memory) and explains the type of context it retrieves (decisions, fixes, preferences). The example GET request also illustrates the call style. No contradiction with 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?

The description is concise and front-loaded with the core purpose. It includes an example and a key prerequisite in two sentences, with no redundant information. Every sentence serves a purpose.

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 tool's purpose, when to use it, a usage example, and an authentication prerequisite. With full parameter documentation, an output schema, and annotations, the description is sufficiently complete. It also positions the tool well relative to its siblings.

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 schema provides detailed descriptions for all three parameters (limit, query, project), so the description adds little beyond restating that filtering is optional and showing an example that uses 'query.' With 100% schema coverage, the baseline is 3, and the description does not significantly enrich parameter meaning.

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 'Retrieve previously stored memories,' a specific verb and resource. It also specifies optional filtering by search query and project, and gives a concrete use case (restoring context at the start of work). This clearly distinguishes it from sibling tools 'remember' and 'forget.'

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 says to call it 'at the start of work on a known project' to restore context, which is clear when-to-use guidance. It does not explicitly name alternatives, but the phrasing and sibling names imply that 'remember' is for storing and 'forget' for deleting. The example and note about needing a workspace/key add practical context.

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