create_milestone

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

Description only states 'Create a new milestone', which is consistent with readOnlyHint=false. No additional behavioral context (e.g., side effects, permissions, limits) beyond annotations. Annotations already indicate it's not read-only, not destructive, not idempotent, and open-world.

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?

Single sentence of 11 words, no redundancy. However, it lacks usage guidelines that could make it more helpful without being verbose.

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 5 parameters, no output schema, and sibling tools, the description is minimal but adequate. It states the overarching purpose but doesn't elaborate on context (e.g., when to set status or due_date). Schema covers details.

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 the schema already documents parameters. The description adds no parameter-specific meaning. Baseline 3 is appropriate.

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 states 'Create a new milestone for organizing tests by releases or sprints', which clearly specifies the verb (create) and resource (milestone) and distinguishes it from other create tools by mentioning its purpose (organizing tests).

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 explicit guidance on when to use this tool versus alternatives like create_case or create_plan. The purpose implies using it for milestones in testing, but no when-not-to-use or comparison to siblings.

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