Run Dataview Table Query

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

Annotations already indicate read-only, non-destructive, and idempotent behavior. The description adds valuable context about vault selection (session-active vault vs. explicit vaultPath argument) and plugin dependencies, which goes 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?

The description is concise at three sentences, with the first sentence front-loading the purpose and structure, followed by usage guideline and vault selection note. Every sentence provides essential information without 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?

The tool has an output schema, so return values are covered. The description explains vault behavior and plugin requirements. Minor gap: no mention of error handling or limitations, but for a read-only query tool this is acceptable.

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?

Input schema provides full descriptions for all 5 parameters (100% coverage). The description does not add extra semantic value beyond restating the TABLE query structure, so baseline score of 3 applies.

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 identifies the tool as a convenience wrapper for Dataview TABLE queries, specifying the DQL structure (fields, FROM, WHERE, SORT, LIMIT). It distinguishes from other dataview tools like dataview.query or list-based tools by stating 'Use this when you need structured columnar output.'

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?

The description provides a clear use case ('when you need structured columnar output') and notes plugin requirements. However, it does not explicitly mention when not to use this tool or compare it to siblings like dataview.query, which could lead to ambiguity.

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