obsidian_search_tasks

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

With no annotations, the description carries full burden. It states the tool returns a JSON array of matching tasks, implying a read-only operation, but does not disclose additional behavioral traits such as performance, side effects, or rate limits. The description is accurate but minimal.

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 front-loaded with the purpose in the first sentence, followed by a structured parameter list. It is efficient but slightly verbose with repeated 'Filter tasks...' patterns. Could be more bullet-like, but remains clear and scannable.

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 6 parameters, an existing output schema (though not detailed), and many sibling tools, the description covers all arguments and the return type. It does not address sorting or pagination, but for a search tool, the provided info suffices for basic use. Reasonably complete.

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?

Despite 0% schema description coverage, the description's docstring provides meaningful explanations for all 6 parameters (e.g., 'Filter tasks due before this date'). This adds semantic value beyond the raw schema, though the schema already includes defaults and types. The description compensates well for the schema gap.

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 'Search for tasks across the vault' with a specific verb and resource. It distinguishes from sibling tools like obsidian_get_tasks (which likely retrieves all tasks) by listing filter parameters, making the tool's purpose 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?

The description implicitly tells when to use the tool by enumerating filter parameters (status, tag, dates, text). However, it lacks explicit guidance on when not to use it or alternatives (e.g., preferring get_tasks for unfiltered retrieval). The usage context is clear but not definitively contrasted with siblings.

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