roadmap_next

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

Discloses selection logic (highest-priority in-progress first, then planned sorted by priority). No annotations, so description carries burden. Lacks details on edge cases (e.g., no items) or side effects, but overall transparent.

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?

Two sentences, front-loaded with purpose and then details. No fluff, but could be slightly more structured (e.g., separate usage note). Efficient overall.

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?

Adequate for a simple tool: covers action, selection logic, and suggested usage. Missing return format and handling of empty results, but given no output schema and simple parameters, it's minimally complete.

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 clear descriptions for instance_id and tag. Description adds no extra parameter meaning, so baseline 3 is appropriate.

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?

Description clearly states it gets a single actionable roadmap item, with explicit ordering rule (in-progress first, then planned by priority). Distinguishes from siblings roadmap_list (list all) and roadmap_add (add item). Specific verb and resource.

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?

Provides clear usage context: 'Call at session start to immediately know what to work on next.' Does not explicitly exclude other scenarios or mention alternatives, but implied differentiation from roadmap_list is strong.

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