List Notes By Tag

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

Annotations already mark it as read-only and idempotent, but the description goes further: it discloses that the tool is a convenience wrapper, returns the same shape as dataview.query, requires specific plugins, and operates on the session-active vault unless vaultPath is provided. These are significant behavioral details not encoded in 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?

The description is compact and front-loaded: it states the core action, then usage guidance, then vault behavior. Every sentence adds value, no filler or repetition.

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 tool's moderate complexity, the full schema coverage, the presence of an output schema, and rich annotations, the description covers all necessary aspects: purpose, usage, requirements, vault selection, and expected return shape. Nothing an agent needs to call it correctly is missing.

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?

The input schema already has 100% coverage with clear descriptions for all four parameters (e.g., tag accepts leading `#`, sortBy is a DQL clause body). The description does not add further parameter-specific detail; it only restates the optional clauses in prose, so a baseline 3 is appropriate.

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 wrapper around `LIST FROM #tag` and explicitly contrasts it with raw DQL ('Use this instead of authoring raw DQL when filtering by a single tag'), making its purpose and differentiation from sibling tools like dataview.query unambiguous.

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?

Provides explicit when-to-use guidance ('when filtering by a single tag') and names the alternative (raw DQL). It also adds prerequisites (Dataview and Local REST API plugins) and explains vault selection behavior, leaving no ambiguity about when to call it.

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