recent_activity

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

With no annotations, the description fully carries transparency. It reveals that the tool works without LLM (structured listing) or with LLM enhancement (summary), and that results are grouped by project regardless of semantic relevance. No side effects are noted, but for a read-only tool this is sufficient.

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 concise with three key sentences that front-load purpose and usage. It could be slightly tighter but is well-structured and efficient.

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 output schema covers return values, the description adequately covers overall behavior, grouping, time window, and mode. It lacks details on error handling and full parameter options, but is complete enough for typical use.

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 0%, so the description must compensate. It explains 'hours' (last N hours) and 'project' (grouped by project) but does not explicitly detail 'format' or 'max_memories'. The reference to 'structured listing' vs 'summary' hints at format, but mapping is incomplete.

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 'Get a summary of recent memory activity across projects' with a specific verb and resource. It distinguishes itself from sibling tools like search by emphasizing that it captures recent context that semantic search would miss.

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 instructs to 'CALL THIS AT THE START OF EVERY SESSION' and explains why it is preferred over semantic search. However, it does not explicitly list alternative sibling tools or state when not to use it.

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