list_notes_by_folder_dql_tool

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

No annotations exist, so description carries full burden. It discloses the prerequisite (Dataview plugin) and states the return format. However, it does not mention side effects, permissions, or whether it is read-only, which would enhance transparency.

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?

Description is fairly concise with clear sections (purpose, when-to-use, returns). It is front-loaded with key action. Could be slightly tighter by removing some redundancy.

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 no output schema, description explains return value ('list of matching notes with Dataview metadata'). Covers prerequisites, inputs, and high-level behavior. Lacks details on limit usage or error cases.

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?

With 80% schema coverage, the description adds little beyond schema: 'optional filtering and sorting' maps to where_clause and sort_by. It does not provide constraints, syntax examples, or defaults beyond schema.

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?

Description starts with clear verb and resource: 'List notes in a folder using DQL'. It distinguishes from siblings like list_notes_tool by specifying the method (DQL) and prerequisites (Obsidian + Dataview plugin).

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?

Includes a 'When to use' section with three specific scenarios, providing context for appropriate usage. However, it does not explicitly mention when not to use or compare to alternatives like list_notes_tool.

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