obsidian_list_tasks

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

The description aligns with annotations (readOnlyHint=true) and adds that the tool lists tasks with filters. However, it does not disclose behavior like pagination (limit/offset) or that only tasks from markdown files are considered, beyond what is implicit. With annotations already covering safety, the description adds modest value.

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 a single sentence with no redundancy. Every word is necessary to convey the tool's core function. It is optimally concise.

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?

Despite having 8 parameters and no output schema, the description does not explain the return format (e.g., which task fields are returned) or how to handle pagination. Given the tool's complexity and the lack of output schema, the description is insufficient for an agent to fully understand the tool's behavior.

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 very low (13%), so the description must compensate. It maps user-facing filters ('status, tags, folder, and due dates') to parameters (checked, tag, pathPrefix, dueBefore/After), providing meaning that the schema lacks. It omits vault, limit, and offset, but these are less critical for filtering intent.

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 the verb 'List', the resource 'Markdown tasks', and the scope 'across the vault'. It also mentions specific filter dimensions, distinguishing it from sibling tools like obsidian_query_notes which are more general.

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?

No guidance is provided on when to use this tool versus alternatives such as obsidian_query_notes or obsidian_search for task-related queries. The description lacks usage context or exclusion criteria.

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