roadmap_list

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

No annotations, but description clarifies it's a read-only list operation (safe), with default filters and sorting. Lacks details on authentication or potential side effects, but as a list tool, these are 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?

Two sentences, front-loaded with the main action and filters. No redundant information.

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?

Covers purpose, filtering, sorting, and automatic invocation. Does not mention return format or pagination, but for a list tool this is acceptable given schema coverage.

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?

Input schema covers all parameters with descriptions. The description adds value by explaining the 'open' status filter and sorting order beyond 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?

Description clearly states the tool lists roadmap items with optional filters (status, priority, tag, milestone) and sorting order. It distinguishes itself from sibling tools like roadmap_add and roadmap_next.

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?

Mentions that it's called automatically by session_start to show open work, providing context. However, it doesn't explicitly contrast with alternatives like roadmap_next.

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