linear_createMilestone

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

Annotations already indicate this is a non-read, non-destructive mutation. The description adds the basic fact that a new milestone is created, but does not disclose additional behavioral context such as permissions, side effects, idempotence nuances, or response behavior. With annotations in place, this is adequate but not enriched.

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, direct sentence with no filler or redundant detail. It front-loads the action and resource, which is appropriately concise for a straightforward create operation.

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?

For a simple create tool with full schema coverage, an output schema, and clear purpose, the description is largely complete. It does not spell out prerequisites like needing a valid projectId in prose, but the required parameter and schema already communicate that. The absence of further prose is not a critical gap.

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?

Schema description coverage is 100%, so all five parameters (name, projectId, sortOrder, targetDate, description) are already documented in the input schema. The description adds no parameter-level meaning, but compensation is unnecessary given the full schema 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 clearly states a specific action ('Create') applied to a specific resource ('new project milestone in Linear'). It distinguishes this tool from the milestone-related siblings (getMilestones, updateMilestone, archiveMilestone) and from other create tools in the list, making the purpose 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 gives clear context: use this when creating a new milestone. It does not explicitly list alternatives or exclusions, but no other create-milestone sibling exists, and the get/update/archive siblings imply different lifecycle stages, so an agent can infer appropriate usage without further guidance.

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