mem_recent_changes

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

With no annotations, the description provides substantial behavioral context: it returns a changelog of specific categories. It implies a read-only operation without side effects. However, it does not disclose how the 'last stable context sync' is determined or whether results are scoped to the project/session.

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 a single, well-structured sentence that front-loads the key action and enumerates return categories. No unnecessary words or repetitions.

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 lack of output schema and 28 sibling tools, the description could clarify how this tool fits into the workflow (e.g., when to use after a sync) and explain return format. It lists categories but not structure. Adequate but not fully complete.

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 description provides no information about the two parameters (project_key, session_id) beyond what the schema offers. With 0% schema description coverage, the description fails to add meaning—e.g., what session_id does or why project_key is required.

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: returning changes since the last stable context sync, listing specific categories (new pending items, resolved work, blocker changes, DoD gap changes, new decisions). This is a specific verb-resource combination that distinguishes it from siblings like mem_get or mem_recent, which do not mention sync-related changelogs.

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 after a stable context sync, but does not explicitly state when to use this tool versus alternatives like mem_recent (recent changes) or mem_get (generic retrieval). No exclusions or prerequisites are given, leaving ambiguity for the agent.

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