github_issues_create_milestone

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

The description implies a write operation but fails to disclose any behavioral traits such as required permissions, side effects (e.g., creation triggers notifications), rate limits, or error conditions. With no annotations, the description should provide this context.

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 three words, which is efficient. However, it lacks any structure (e.g., no separation of purpose from usage). Still, it avoids unnecessary verbiage.

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 tool has three parameters, no output schema, and no annotations, the description is insufficient. It does not explain the 'body' parameter (a JSON object), the scope of the milestone (repository), or what the tool returns.

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 covers 100% of parameters (owner, repo, body). The description adds no additional meaning beyond what the schema already provides. The baseline of 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 'Create a milestone' clearly states the action (create) and the resource (milestone). It is specific and unambiguous, but does not add context about the repository or differentiate from other milestone operations like update or delete. However, the verb alone distinguishes it.

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 on when to use this tool instead of alternatives such as update_milestone or delete_milestone. There is no mention of prerequisites, permissions, or typical use cases.

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