list_notes

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

With no annotations, the description must carry the burden. It discloses the ordering and filter behavior but does not mention pagination (though limit/offset are in schema), potential performance implications, or what happens when no notes match. It's a read-only operation, but that's inferred. No contradictions.

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?

One concise sentence, well-structured, with key attributes (ordering, filter) front-loaded. No unnecessary words.

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 simple read-only list tool with optional filters and pagination, the description is adequate but leaves minor gaps: it doesn't mention what is returned (e.g., note object vs metadata), and given no output schema, that info is missing. It could specify that it returns note summaries or full notes, but overall it's sufficient for an agent to call it.

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 covers 'tag' with no descriptionstitution, but 'limit' and 'offset' have descriptions. With 67% coverage, the description adds optional filter context for 'tag' but doesn't elaborate on semantics beyond the schema. Baseline 3 is appropriate given partial coverage.

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 states a clear verb ('List') and resource ('notes') and specifies ordering ('by last change') and an optional filter ('by tag'). It is distinct from siblings like search_notes (which implies search) and get_note, though it doesn't explicitly differentiate them.

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 a simple listing use case and distinguishes it from search_notes by using 'list' versus 'search'. However, it doesn't explicitly state when to use this over search_notes or other list-like tools, nor does it mention alternatives.

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