Task Statistics

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

Disclosures include read-only nature (matching annotations) and the vault override logic. No contradictions with annotations (readOnlyHint, idempotentHint, etc.), and adds value beyond them by detailing the scope and override behavior.

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 brief paragraphs with clear front-loading: first paragraph defines purpose and alternative, second explains vault context. Every sentence adds value, no 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?

Given the output schema exists, return values need not be described. The description covers the tool's function, safety (read-only), parameter usage, and relationship to siblings, making it fully informative for selection and invocation.

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 coverage is 0% for the only parameter 'vaultPath'. The description adds meaning by explaining that it determines which vault to query, overriding the session-active vault. This compensates for the lack of schema description.

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 it returns aggregate task statistics for the whole vault, listing specific counts (total, incomplete, completed, overdue, upcoming, per-priority). It also distinguishes from sibling 'tasks.search' by stating that tool retrieves individual records.

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?

Explicitly states 'Read-only' and provides an alternative ('Use tasks.search to get individual task records'). Also explains the vault selection behavior (session-active vs explicit vaultPath), giving clear context on when to use this tool.

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