roadmap_list

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

The description discloses that results are sorted by priority then creation date, and that it is called automatically, which adds value beyond the schema. However, with no annotations provided, it fails to explicitly confirm read-only behavior, mention any side effects, or note rate limits or authentication requirements.

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?

The description is only two sentences long, front-loaded with the primary purpose, and every sentence provides essential information without redundancy. It is highly efficient and easy to parse.

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?

The description adequately explains the tool's behavior (filtering, sorting, automatic invocation) given the absence of an output schema and the moderate complexity. It could be improved by mentioning the return format or pagination, but it is largely sufficient for selecting and using the 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?

All five parameters are fully described in the input schema (100% coverage), so the description adds minimal new semantic information. It reiterates the filters but does not clarify parameter values beyond what the schema already provides, though it mentions the default status 'open' which is already 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?

The description uses a specific verb-resource pair ('List all roadmap items') and explicitly mentions the optional filters (status, priority, tag, milestone). It clearly distinguishes from sibling tools like roadmap_add and roadmap_update by focusing on listing versus creating or modifying items.

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 states it is 'Called automatically by session_start to show open work,' providing clear context for when it is used. However, it does not explicitly mention when not to use it or suggest alternatives like roadmap_next for single-item retrieval.

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