list_tasks

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

No annotations are provided, so the description carries the disclosure burden. It signals read-only behavior by saying 'Query' and 'Returns a filtered, sorted list.' However, it omits notable default behaviors such as completed tasks being excluded by default, what the sort order is, and whether tags/assignee filters are exact or partial.

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?

Two efficient sentences front-load the action and result, then provide use cases. There is no filler; every phrase contributes to selection or invocation.

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?

With 10 parameters fully documented in the schema and no output schema, the description supplies the key missing context: the task queue source, read-only intent, and usage scenarios. The main omission is out-of-scope behavioral detail like default active-only filtering and sort ordering, which would strengthen completeness.

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 100%, with every parameter having a description, enum, or default, so the baseline is 3. The description adds only high-level filter categories already reflected in the schema and does not repeat detailed parameter semantics.

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 states a specific verb ('Query') and resource ('tasks from the vault's task queue'), and names the filtering dimensions: status, priority, type, or assignee. This clearly distinguishes it from mutation siblings like create_task, update_task, and complete_task.

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 gives concrete usage contexts: 'find available work or monitor progress.' It does not explicitly name alternatives or state when not to use the tool, but the read-only query intent is clear enough to guide selection among the sibling tools.

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