recent_notes

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

No annotations are provided, so the description carries the full burden. It discloses the time window and ordering but doesn't mention whether the result is limited to a folder, how the 'days' filter interacts with the 'folder' parameter, whether deleted or archived notes are excluded, or what the return format looks like. For a read tool, this is a moderate gap.

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 concise sentence that front-loads the core behavior (recency filter) and ordering. It earns its place with no filler, though it could add a brief note about the folder parameter without becoming verbose.

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?

With no annotations, no output schema, and 0% schema description coverage, the description is too thin. An agent cannot tell whether 'folder' is a filter or a target, what the default behavior is (though defaults exist in the schema), or what the response shape is. For a tool with three parameters, this is incomplete.

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 'days' (time window) and 'limit' (implicitly via 'newest first' but not explicitly), but it doesn't explain the 'folder' parameter at all. The description adds some meaning for 'days' but leaves 'folder' and 'limit' semantics unclear.

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 states a specific verb ('modified') and resource ('notes') with a clear time window ('last N days') and ordering ('newest first'). It distinguishes itself from siblings like list_notes and stale_notes by focusing on recency, though it doesn't explicitly name an alternative.

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 a use case: retrieving recently modified notes. However, it doesn't explicitly state when to use this tool versus alternatives like list_notes, find_notes, or search_notes, nor does it mention any exclusions or prerequisites.

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