process

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

With no annotations provided, the description carries the full burden. It discloses behavioral traits such as analyzing memories, asking clarifying questions, and requiring follow-up calls, which adds context beyond basic functionality. However, it lacks details on permissions, rate limits, or error handling, leaving gaps for a tool with mutation implications.

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 appropriately sized with two sentences that efficiently convey the tool's purpose and workflow. It's front-loaded with the main action and avoids unnecessary details, though it could be slightly more structured for clarity.

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 complexity (involving analysis and iterative refinement), no annotations, and no output schema, the description is moderately complete. It outlines the process but lacks details on return values, error conditions, or full behavioral context, making it adequate but with clear gaps.

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 schema already documents both parameters. The description adds minimal value by mentioning 'context' usage for answers, but doesn't provide additional syntax or format details beyond what the schema specifies, aligning with the baseline for high coverage.

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 clearly states the tool's purpose: 'Review and refine existing memories' with specific actions like analyzing for quality, duplicates, and gaps. It distinguishes from siblings like 'remember' (create) and 'recall' (retrieve) by focusing on refinement, though it doesn't explicitly name alternatives.

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 implies usage through phrases like 'Call again with answers to apply refinements,' suggesting a two-step workflow. However, it doesn't explicitly state when to use this versus alternatives like 'forget' or 'process_answers,' leaving some ambiguity about the tool's specific context.

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