get_recent_notes

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It fails to state whether the tool is read-only, what the return format is (e.g., metadata vs. full content), whether results are sorted by modification time, or what 'recently' means. These are significant gaps for a tool operating on notes.

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 two concise sentences with no wasteful wording. The first sentence immediately states the core action, and the second adds a relevant use case, making it well-structured and front-loaded.

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 is relatively simple with well-documented parameters, but the lack of an output schema and annotations leaves ambiguity about the return format (e.g., note paths vs. content) and the definition of 'recently.' It is minimally viable but has clear gaps that could be addressed.

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 input schema has 100% description coverage for both parameters (limit and folder), so the schema already provides the necessary meaning. The description adds no additional parameter context, and the baseline for full schema coverage is 3.

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 'Get a list of recently modified markdown notes,' which uses a specific verb and resource, and the modifier 'recently modified' distinguishes it from generic list tools like list_files and list_all_files. The sentence 'Useful for finding notes you've worked on recently' reinforces its intended purpose.

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 provides a clear context for use: 'Useful for finding notes you've worked on recently.' However, it does not explicitly mention alternatives or when not to use the tool, so it stops short of a full 5.

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