List Notes By Tag

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

Annotations already declare readOnlyHint=true and idempotentHint=true. The description adds valuable behavioral context: vault selection behavior (session-active vault vs explicit vaultPath) and plugin requirements, which go beyond annotations.

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 paragraphs with zero fluff. The first paragraph covers purpose and usage, the second covers vault behavior. Every sentence adds value.

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?

Given the complexity (wrapper around DQL with optional clauses, vault dependency, return shape), the description is complete. It references the output shape to `dataview.query`, and output schema exists separately.

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%. The description adds meaning beyond schema by clarifying that tag can include or omit the leading `#`, and that whereClause, sortBy, limit are clause bodies without keywords (e.g., 'without the WHERE keyword').

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 it is a convenience wrapper for `LIST FROM #tag`, specifying the verb (list), resource (notes by tag), and optional clauses. It differentiates from sibling tools like `dataview.query` and `dataview.listByFolder`.

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?

It provides explicit guidance: 'Use this instead of authoring raw DQL when filtering by a single tag.' It also mentions required plugins and vault selection behavior, though it does not explicitly state when not to use it (e.g., multiple tags).

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