roadmap_add_node

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

Discloses return value (the id), segment inheritance, and priority range. No annotations present so description does the job. Could mention validation (e.g., parent existence).

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 concise sentences: first states purpose, second details key parameters. No unnecessary words.

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 main behavior and key parameters; return value specified. Lacks explanation of 'segment' and 'title' fields, but overall adequate for a node addition tool with no annotations.

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?

With 0% schema coverage, description compensates by explaining kind values, parent_id nesting, priority scale, and return value. Title and segment not fully described, but segment inheritance is noted.

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 'Add a node to the roadmap tree' and enumerates valid kinds. Distinct from siblings like roadmap_view or roadmap_update.

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?

Implies use for adding nodes; explains nesting with parent_id and segment inheritance. No explicit when-not or alternatives, but context from siblings is clear.

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