roadmap_add

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

Describes that items persist across sessions and editors, indicating longevity. However, no annotations are present, and the description does not disclose potential side effects, limits, or concurrency issues.

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 with no redundancy. First sentence defines purpose and persistence, second sentence offers usage examples and sibling references. Highly efficient.

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?

Covers purpose, persistence, and usage scope. With 6 parameters and no output schema, it omits what the tool returns upon success (e.g., confirmation or item ID). Otherwise 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 descriptions for each parameter. The description does not add meaningful extra guidance beyond examples (e.g., tags). Baseline 3 due to full schema coverage.

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?

Clearly states it adds an item to the persistent project roadmap, specifying verbs and resource. Distinguishes from sibling tools roadmap_list and roadmap_next.

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?

Explicitly says to use for features, bugs, refactors, and any planned work. References sibling tools for other actions, but lacks explicit when not to use.

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