reopen_milestone

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It names the action but doesn't disclose side effects, permissions required, reversibility, or what happens if the milestone isn't closed. The single sentence is minimally informative and leaves the agent guessing about the operation's behavior.

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 efficient sentence with no filler. It's appropriately short for such a focused operation, though the brevity comes at the cost of behavioral and parameter context.

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?

The tool has three required parameters, no output schema, and no annotations, yet the description provides no usage context, no parameter hints, no return-value info, and no behavioral detail. It's the minimum viable statement of what the tool does, but an agent has almost nothing to go on for correct invocation beyond the parameter names.

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 0%, and the description adds nothing about the three required parameters (owner, repo, milestone_id). An agent must infer that owner/repo identify the repository and milestone_id identifies the target milestone, which is guessable but not documented.

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 a specific verb and resource ('Reopen a closed milestone'), making the core action clear. However, it doesn't differentiate this tool from sibling tools like list_milestones or forgejo_status, which also operate on milestones/repositories, so the agent must infer the distinction from the tool name alone.

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 given about when to use reopen_milestone versus alternatives. The description doesn't mention prerequisites (e.g., milestone must exist and be closed), error conditions, or any context that would help an agent decide this is the right tool.

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