List notes

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

With readOnlyHint=true already covering the safety profile, the description adds value by disclosing that responses contain only summaries (no bodies) and are sorted by recency. This is concrete behavioral context beyond the annotation; it does not describe pagination or the contents of a summary, which keeps it from a 5.

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?

Two sentences with no redundancy: the first packs the operation, output scope, and sort order; the second adds a single piece of usage guidance. Every clause earns its place, and key facts are front-loaded.

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 two-optional-parameter list tool with a read-only annotation, the description covers the core invocation needs: what is returned (summaries), what is excluded (bodies), and ordering. The only gap is that 'summaries' is not defined (e.g., which fields appear), and there is no output schema to compensate, so it is not a 5.

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 100%: both 'tag' and 'limit' have clear inline descriptions, so the schema carries the parameter documentation. The tool description itself adds no parameter-level meaning, matching the baseline of 3 for high 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'), resource ('notes'), and immediately scopes the result to 'summaries (no bodies)', which differentiates it from read_note and search_notes. It also pins the ordering to 'most recently updated first', leaving no ambiguity about what the tool does.

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?

'Use this to get your bearings before reading or searching' explicitly frames when to call it, positioning it as the orientation step ahead of content retrieval and search. It implies but does not explicitly name the sibling alternatives (read_note for full bodies, search_notes for search), so it stops short of a full when-not/alternatives breakdown.

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