roadmap_list

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

Discloses sorting behavior and the automatic call from session_start. While no annotations exist, the description adequately implies a read-only operation without side effects.

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?

Three concise sentences, each adding distinct information: function with filters, sorting behavior, and automatic invocation. No redundant or vague statements.

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?

Lacks description of return structure (fields of each item). While sorting and filters are covered, the absence of output schema or return details leaves partial gap. Adequate but not complete for a list tool.

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 100% with descriptions for each parameter. The description adds value by explaining the 'open' status filter and the sorting order, which are not present in 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?

Clear verb 'list' with resource 'roadmap items'. Specifies optional filters (status, priority, tag, milestone) and sorting order, distinguishing from sibling tools like 'roadmap_add' and 'roadmap_update'.

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?

States it is 'Called automatically by session_start to show open work', providing context for its use. Does not explicitly exclude alternative tools, but the description implies it is the default list function.

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