Get one roadmap feature

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

No annotations are provided, so the description carries the burden. It adds that the output is 'full detail' and that the ID is numeric, but it does not disclose behavior such as error handling for invalid IDs or the exact response shape. This is a minimal but adequate disclosure for a simple read operation.

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?

The description is a single concise sentence that immediately states the tool's purpose and the key parameter. No unnecessary information or repetition.

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 output schema, 'full detail' gives only a vague idea of the return content. Missing details like not-found behavior and response fields make it incomplete, though the tool is simple enough that the description is acceptable.

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?

The schema already describes the 'id' parameter as a 'Roadmap feature ID' with 100% coverage. The description adds only 'numeric', which is redundant with the integer type. No new semantic information beyond the schema is provided.

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 clearly states the tool returns 'Full detail for a single roadmap feature' by ID, distinguishing it from sibling tools like search_roadmap and list_recent_changes which handle collections or searches.

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?

The description implies you should use this tool when you have a known numeric feature ID, but it does not explicitly mention alternatives or contexts like searching when the ID is unknown. No exclusion criteria are given.

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