Get Recent Notes

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

Beyond annotations (readOnlyHint, idempotentHint), the description adds ordering behavior and the since filter format with examples. It could mention edge cases like invalid since input, but overall adds useful context.

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 three sentences with a clear front-loaded first sentence. No wasted words; every sentence adds value (purpose, details, use cases).

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 description explains ordering and filtering well, but does not mention the folder parameter (present in schema). For a list tool with no output schema, it is mostly complete but missing that detail.

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?

Input schema coverage is 100%, so the description adds minimal new information. It reiterates the since filter format already in the schema, but does not enhance understanding of limit or folder. Baseline 3 holds.

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 lists notes ordered by most-recently-modified first, which distinguishes it from siblings like list_notes (likely no ordering) and search_notes (keyword-based). It provides specific verb and resource.

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 gives explicit use cases: 'surface what you've been working on, build a 'what changed this week' digest, or pick targets for review.' It implies when to use but does not explicitly state when not to use or name alternatives, so 4 is appropriate.

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