get_design_roadmap

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

Describes the roadmap as phased with goals and docs, implying sequential use. Lacks explicit mention of output format or permissions, but for a no-annotation tool, adds substantial value.

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?

Three efficient sentences, no redundancy. Purpose is front-loaded, and instructions are clear.

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 only one parameter and no output schema, the description fully explains the tool's purpose and usage. Complete for the given complexity.

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?

Single parameter project_type with enum. Schema already covers meaning; description reinforces by listing example values in context. Adds marginal improvement.

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 the tool provides a phased expert design process for specific project types. Differentiates from siblings like get_design_doc by specifying it's the first step before fetching phase docs.

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 'Use this FIRST when starting any design project, then fetch phase docs as you reach them.' Provides strong context on when to use and what to do next.

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