recent

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

Discloses that the tool only returns live entries and hides archived ones. Describes behavior of group_by_domain and limit. No annotations provided, so description carries full burden. Lacks mention of authentication or rate limits, but adequate.

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?

Contains unnecessary meta-instructions about how to present information (e.g., 'Never acknowledge...'), which are not about the tool itself. Could be more concise by removing these lines; otherwise front-loaded with 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?

Explains filtering, grouping, defaults, and that only live entries are returned. Suggests alternative tools for archived memories. No output schema, but for a list tool, the description is reasonably complete. Minor gap: no detail on output format.

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%, but description adds significant meaning: explains default limit (10 or 5 per domain), clarifies that group_by_domain is ignored when domain is specified, and provides contextual detail beyond schema.

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?

States 'List the most recently added or updated memories, optionally filtered by domain.' Clearly identifies verb and resource, and notes optional filtering. Does not explicitly differentiate from siblings like 'history' or 'recall', but the purpose is specific.

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?

Provides explicit guidance: 'Good for session orientation.' Also advises considering alternatives ('whats_stale or forgotten') when results are missing, clearly indicating when not to use this tool.

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