notes_get_recent_notes

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

With no annotations provided, the description carries full responsibility for behavioral disclosure, and it only states the core listing action. It does not reveal whether results include note bodies, how limit is applied, ordering of recent notes, or any side-effect safety details.

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?

One sentence with no redundant wording, and the key scope ('recently modified', 'last N days') is front-loaded. Every word earns its place.

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?

The tool has no output schema and no annotations, so the description is the only source for result semantics. It is too thin to fully support correct invocation, particularly around limit, include_body, and the meaning of 'modified'.

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 provide parameter semantics; it only grounds 'days' as the N in 'last N days'. 'limit' and 'include_body' remain unexplained, leaving the agent to guess at valid usage.

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?

Description uses a specific verb and resource ('List ... notes') and adds a defining temporal scope ('recently modified ... last N days') that separates it from sibling tools like notes_list_notes and notes_search_notes. An agent can tell what operation this performs without opening the schema.

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 temporal qualifier implies the use case: retrieving notes changed within a recent window. However, the description does not state when to prefer this over notes_list_notes or notes_search_notes, nor when it should not be used.

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