list_notes

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

The description discloses that results come from an index with up to 5-minute lag, a key behavioral trait not captured elsewhere. No annotations are provided, so this adds necessary transparency.

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 structured with a clear first sentence and separated argument details. It is mostly concise, though the args section could be more streamlined.

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 covers purpose, filtering, and indexing lag. Output schema exists so return values are handled. Missing pagination details, but overall complete for a list tool.

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%, and the description fully explains each parameter: folder path semantics, limit default, tags matching logic, and frontmatter strict type match. This adds significant meaning beyond the schema.

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 in a vault folder sorted by most recently modified. It uses specific verb-resource combination and distinguishes from siblings like keyword_search.

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 explains when to use it (list notes with optional filters) but does not explicitly mention when not to use it or suggest alternative tools for specific needs.

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