obsidian_search_dataview

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

Annotations already indicate the tool is read-only and non-destructive. The description adds that it uses the 'search endpoint', but does not elaborate on return format, pagination, or potential side effects. With annotations covering safety, the description adds minimal behavioral context.

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 single-sentence description is very concise and front-loaded with the key action. However, it may be too brief, sacrificing clarity and completeness for brevity.

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 runs a complex query (Dataview DQL) and has no output schema, the description should at least hint at the return format or provide examples. It is incomplete, lacking usage context, parameter details, and result expectations.

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 0%, so the description must clarify parameters. It mentions running a query but does not explain the 'query' string format (e.g., DQL syntax) or the 'timeoutMs' parameter beyond what the schema provides. The parameter names are somewhat self-explanatory, but the description adds no extra meaning.

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 that the tool runs a Dataview DQL query, which is a specific type of query. It distinguishes this from other search tools like obsidian_search or obsidian_search_jsonlogic by specifying 'Dataview DQL', but does not explicitly differentiate from siblings.

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 no guidance on when to use this tool versus the many sibling search tools (e.g., obsidian_search, obsidian_search_paths, obsidian_query_notes). There is no hint about prerequisites or context, leaving the agent to guess.

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