create_milestone

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a new milestone' implies a write/mutation operation but provides no information about permissions required, whether the creation is reversible, what happens on success/failure, rate limits, or any side effects. For a mutation tool with zero annotation coverage, this is completely inadequate.

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 at just three words, which could be appropriate if it were more informative. However, this conciseness comes at the cost of under-specification rather than efficient communication. The structure is simple but lacks the necessary information density for a tool with multiple parameters and sibling alternatives.

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?

This is a mutation tool with 3 parameters, no annotations, no output schema, and multiple sibling alternatives, yet the description provides minimal information. It fails to explain what a milestone is in this context, how it differs from other project management artifacts, what the parameters mean, or what happens after creation. For a tool of this complexity and context, the description is completely inadequate.

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 description provides zero information about parameters. With 3 parameters (title, description, dueDate) and 0% schema description coverage, the schema only shows data types without explaining what these fields represent or their constraints. The description doesn't mention any parameters, their purposes, or provide any semantic context beyond what's in the bare 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 'Create a new milestone' is a tautology that merely restates the tool name without adding specificity. It doesn't distinguish this tool from sibling tools like 'create_project', 'create_sprint', or 'create_roadmap' that also create different resources. While the verb 'create' is clear, the description fails to provide meaningful differentiation from other creation tools in the server.

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 absolutely no guidance about when to use this tool versus alternatives. With multiple sibling creation tools (create_project, create_sprint, create_roadmap, create_issue, etc.), there's no indication of when a milestone is appropriate versus other project management artifacts. No prerequisites, context, or exclusions are mentioned.

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