roadmap_show

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing. It does not state that the call is read-only, whether the roadmap must exist, what error occurs for an unknown id, or what the response contains. Only the word 'Show' weakly implies a read.

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?

It is a single short sentence with no wasted words and is front-loaded, but its brevity comes from under-specification rather than efficiency.

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?

For a tool with one undocumented parameter, no annotations, and no output schema, the description should at least clarify what is retrieved and what the identifier refers to. Neither is covered, leaving the agent to guess at call correctness.

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% and the description never mentions the roadmap_id parameter or its expected format (id, slug, name?). 'One Roadmap' only faintly implies that an identifier selects a single record, so the description does not compensate for the schema gap.

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 verb (Show) and a resource (Roadmap outcome) with singular scope, so an agent can infer it retrieves one roadmap record. However, 'outcome' is undefined terminology and the description does nothing to distinguish it from close siblings like roadmap_list, roadmap_snapshot, roadmap_events, or aiworkhub_dashboard_roadmap_detail.

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 and no mention of alternatives. With roadmap_list, roadmap_snapshot, and roadmap_events all present, an agent has no stated basis for choosing roadmap_show over them.

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