List notes

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

readOnlyHint=true already tells the agent this is a safe read. The description adds genuinely useful traits beyond that: the default sort order ('newest first') and the constraint that only one tag can be supplied. It does not mention pagination, result limits, or ordering controls, which matters for a list endpoint.

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 short sentences, zero waste, with the ordering behavior front-loaded and the filter constraint second. Nothing is repeated from the name or title.

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 zero-required-parameter read tool with an annotated safety profile and no output schema, the description covers what is needed to invoke it. The only real gap is the absence of any hint about result size or pagination for a potentially unbounded list.

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% for the single 'tag' parameter, so the baseline is 3. The description adds a small nuance the schema does not convey: only a single tag is accepted, not a set.

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?

States a specific verb and resource ('List notes') plus ordering ('newest first') and an optional filter. It is clear on its own, but it never differentiates itself from the sibling search_notes, which an agent could easily confuse with a filtered list.

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?

'Optionally filter by a single tag' implies the intended usage, but there is no explicit guidance on when to use this versus search_notes or when a tag filter is preferable to a search query. Usage must be inferred.

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