delimit_memory_recent

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

With no annotations provided, the description only says 'get recent work summary', which implies a read operation but gives no details on safety, authentication, rate limits, or side effects. The behavioral transparency is minimal beyond what the name suggests.

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 very concise at two sentences, front-loading the purpose. Every sentence adds value, and there is no unnecessary information. It earns points for efficiency.

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?

For a simple tool with one optional parameter and no annotations, the description is adequate but has clear gaps. It does not describe the output format or how this tool relates to delimit_memory_search, which would be helpful for an agent to select the correct 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?

The input schema covers the single parameter 'limit' with a clear description, so schema coverage is 100%. The description does not add any additional meaning to the parameter beyond what the schema already provides, so it meets the baseline but does not exceed it.

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 retrieves recent work summaries from memory ('Get recent work summary from memory'), which is a specific verb+resource combination. However, it does not explicitly differentiate from the sibling tool 'delimit_memory_search', though the mention of 'Pro: structured search' hints at a tier-based distinction.

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 context by contrasting 'Free: retrieve recent entries' with 'Pro: structured search', suggesting this tool is for simple recent retrieval. However, it does not explicitly state when not to use this tool or name an alternative, leaving ambiguity.

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