List Markdown 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 mentions 'recent' but does not explain how recency is determined, what fields are returned, or whether the list contains full content or summaries. The behavioral scope is under-specified.

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, well-structured sentence with no redundant words. It front-loads the verb and provides the key resource and source location, earning a top score for efficiency.

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 simple but there is no output schema, so the description should explain what the list returns. It does not describe the response format, ordering, or meaning of 'recent', leaving the agent uncertain about the tool's output. This is a significant gap for a tool with no structured return information.

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%, yet the description does not mention the 'limit' parameter at all. The agent only knows its type, default, and constraints, but not what it controls (e.g., number of notes returned). The description fails to compensate for the lack of schema descriptions.

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 action ('List') and the resource ('recent Markdown notes from NOTES_DATA_DIR'), which is specific and distinguishes the tool from siblings notes_save and notes_read.

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 when to use the tool (to get an overview of notes) but does not explicitly contrast it with notes_save or notes_read, nor does it mention any exclusions such as returning full content versus metadata.

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