create_milestone

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

The description discloses the default dry_run=true behavior and preview functionality, adding context beyond the readOnlyHint=false annotation. It does not cover all behavioral aspects but adequately explains the key safety mechanism.

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 extremely concise: two sentences that front-load the primary action and immediately explain the essential dry_run behavior. No wasted 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?

Given no output schema, the description explains the preview return. It covers the core workflow but could mention that this is for group milestones (implicit via group_id). Adequate for a creation tool with good parameter descriptions.

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 input schema has 100% coverage with descriptions for all six parameters. The description adds minimal extra meaning beyond highlighting dry_run's default and workflow intent. It meets the baseline but does not significantly augment the schema.

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 'Creer un nouveau milestone' (create a new milestone), identifying the verb and resource. It does not explicitly differentiate from sibling tools like create_project_milestone, but the purpose is unambiguous.

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 provides usage guidance: dry_run defaults to true for preview, and should be set to false after confirmation. This outlines a safe workflow but does not discuss when to use this tool versus alternatives.

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