roadmap_list

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

No annotations are provided, so the description carries the full burden. It implies a read operation via "List" but never states read-only safety, pagination behavior (limit/offset defaults), how include_archived affects results, or the archived-status filtering semantics. The word "bounded" hints at some restriction but is never explained.

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?

A single short front-loaded sentence with no wasted words, but it is terse to the point of under-specification rather than genuinely efficient. There is nothing misleading, just very little content to structure.

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?

Although an output schema exists so return shape needn't be described, the definition is still incomplete for a four-parameter, annotation-free list tool: no usage context, no parameter meaning, and no behavioral disclosure. An agent could call it, but not confidently or correctly relative to its siblings.

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 0% for four parameters, so the schema offers only names and defaults with no meaning. The description does not compensate at all, never explaining limit, offset, status, or include_archived semantics, leaving the agent to guess at filtering and paging behavior.

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?

It does name a verb and resource ("List ... Roadmap outcomes"), but "bounded repository Roadmap outcomes" is jargon that never clarifies what a Roadmap outcome actually is or what the list contains. It does not distinguish this from siblings like roadmap_show, roadmap_events, roadmap_snapshot, or aiworkhub_dashboard_roadmap_list, so an agent cannot route between them from the description alone.

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?

There is no when-to-use guidance, no prerequisites, and no mention of the alternative roadmap/dashboard list and detail tools. The agent is left to infer that this is the enumeration entry point versus roadmap_show for a single item.

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