list_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 does add return-value details (paths, names, dates, sizes) and implies a read-only operation via the verb 'List,' but it does not explicitly state that it has no side effects or mention any permissions or limitations, leaving some ambiguity.

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, concise sentence that front-loads the core action and resource, then lists capabilities and return fields. Every phrase earns its place with no redundant or filler content.

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?

For a tool with seven parameters and no output schema or annotations, the description covers the essential scope (markdown notes), return fields, and key features (sorting, filtering, pagination). It could be more explicit about default behaviors or the read-only nature, but the schema fills in parameter details, making it adequately complete for a list operation.

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 coverage is 100% for all parameters, so the baseline is 3. The description does not elaborate on parameter semantics, but the schema already provides thorough descriptions for limit, folder, offset, sortBy, recursive, sortOrder, and namePattern, so no additional meaning is required.

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 markdown notes in the vault with sorting, filtering, and pagination, and specifies the return fields (paths, names, dates, sizes). This distinguishes it from sibling list tools like list_daily_notes or list_attachments by focusing on general notes with a specific resource scope.

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 no explicit guidance on when to use this tool versus alternatives such as search_vault or list_daily_notes. It implies usage through its feature list but lacks any when-to-use or when-not-to-use instructions, so the agent receives no decision support.

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