delimit_memory_recent

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

With no annotations, the description fully discloses side effects: 'read-only', calls backend 'backends.memory_bridge.get_recent', and 'Free tier — no license gate'. This goes beyond what the schema provides.

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?

Description is concise (under 100 words), well-structured with labeled sections (When to use, When NOT to use, Sibling contrast, Side effects). Every sentence adds value without redundancy.

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 low complexity (1 param, no required params, output schema exists), the description covers purpose, usage, behavior, and alternatives. No gaps remain.

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 coverage is 100% for the single parameter 'limit'. The description adds 'Default 5' which is already in schema default. No additional semantics beyond schema, so baseline 3 is justified.

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?

Clearly states 'Return the most recent memory entries (Free tier)'. The verb 'Return' and resource 'memory entries' are specific. It distinguishes from siblings like delimit_memory_search and delimit_memory_store by noting the chronological tail vs semantic search.

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?

Explicitly provides when to use ('at session start') and when not to use ('for semantic/structured search' or 'to write'). Also names alternatives (delimit_memory_search, delimit_memory_store).

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