gsd_new_milestone

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

There are no annotations, so the description carries full responsibility for behavioral disclosure. 'Start a new milestone' gives no indication of side effects, state changes, required permissions, or what happens to the current milestone. The tool likely mutates state, but this is not explicit.

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, front-loaded sentence with no filler words. Every word carries meaning, making it highly concise and structurally optimal.

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?

Given the simple schema (1 param) and lack of output schema, the description is still too minimal. It does not explain the milestone lifecycle, when to start a new milestone, or what side effects occur. With many sibling tools, more context is needed to avoid misuse.

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 documents the only parameter 'name' with a description ('Milestone name (e.g. v2.0)'), so schema coverage is 100%. The tool description adds no additional meaning beyond the schema, which is acceptable per the baseline for high 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?

The description 'Start a new milestone' uses a specific verb ('start') and resource ('milestone'), making the core action clear. It does not explicitly differentiate from sibling tools like gsd_complete_milestone, but the word 'new' implies creation rather than completion.

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?

No guidance is provided about when to use this tool versus alternatives, nor are any prerequisites or exclusions mentioned. The usage context must be inferred entirely from the tool name and surrounding siblings.

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