Get Next Task

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

Annotations already declare readOnlyHint and idempotentHint; the description reinforces this with 'Read-only; never edits tasks.md' and adds the concrete behavior of returning a completion marker when no tasks remain. It goes beyond the annotations by revealing the file path and session-context rationale, though it does not cover error cases such as a missing tasks.md.

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 compact sentences with no filler. The core behavior and file path are front-loaded, followed by the usage directive and sibling alternatives, making every clause purposeful.

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 an output schema presentts, annotations covering read-only/idempotent behavior, both parameters documented in the schema, and the description supplying when-to-use plus sibling routing, nothing needed for correct invocation is missing.

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%, so the schema already documents both parameters. The description reinforces that feature must be the exact spec directory name and ties it to the file path vdd/specs/<feature>/tasks.md, adding some context, but it adds no meaningful information about projectRoot beyond the schema.

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?

States a specific verb ('read' and 'return'), a specific resource ('vdd/specs/<feature>/tasks.md'), and the exact result ('the next uncompleted task, or a completion marker when none remain'). It also distinguishes itself from vdd_tasks and vdd_implement, so an agent can select it unambiguously.

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 says when to use it ('Use before each implementation session to keep context isolated'), what to pass ('the exact spec directory name'), and names alternatives for the adjacent operations ('to regenerate the whole list use vdd_tasks, and to execute the returned task use vdd_implement'). This fully routes the agent.

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