roadmap_snapshot

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, yet it discloses nothing about side effects, permissions, whether the operation is read-only, or how expensive/bounded the join is. 'Join' and 'bounded' hint at computation but no concrete behavior is stated.

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 padding, so length is appropriate, but the terseness comes at the cost of clarity rather than from efficient front-loading. The one clause it does contain is jargon-laden.

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?

With no annotations, no output schema, no parameter documentation, and an opaque one-line description, the definition is far too thin for a two-parameter tool that apparently performs a cross-domain join. Nothing tells an agent what it returns or how to invoke it safely.

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 both parameters (limit, include_archived), and the description never mentions them, so it does nothing to explain their meaning or defaults. With two undocumented parameters, the description fails to 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?

The description says it 'joins bounded Roadmap outcomes to canonical Task-DAG lifecycle', which names resources but uses opaque internal jargon and never states what the tool actually produces (a snapshot? a report?). It does not clearly separate this from roadmap_list, roadmap_show, or roadmap_events, so an agent cannot confidently pick it.

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 indication of when to use this tool, when not to, or which sibling to prefer for a plain roadmap view versus this 'join'. The description offers no context, exclusions, or prerequisites at all.

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