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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description is not required to repeat safety traits. However, it adds no behavioral context beyond a restatement of filter dimensions—no mention of pagination, default limits, result ordering, or the fact that all parameters are optional.

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 a single sentence, front-loaded with the verb and resource, and contains no filler. Every word contributes to the core 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?

Despite rich schema and output schema, the description is too sparse for a 10-parameter tool with many siblings. It omits the query parameter, does not explain how filters combine, and offers no selection guidance, leaving an agent to open the schema to understand even basic usage.

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%, so the baseline is 3. The description adds a light grouping of tags/importance/recency as 'metadata,' which is helpful but does not add syntactic, format, or combinatorial details beyond what the parameter descriptions already provide.

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 ('Filter') and resource ('memories') and names three metadata categories (tags, importance, recency) that map to schema parameters. It does not explicitly differentiate from sibling tools like memory.search or memory.query, and it omits the query parameter, so it under-represents the full capability set.

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 gives no guidance on when to prefer this tool over siblings like memory.search, memory.query, memory.list, or memory.hybrid_recall. With a large family of memory tools, an agent cannot determine selection criteria from the description alone.

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