reopen_epic

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

Annotations only include readOnlyHint=false, meaning it's a write operation. The description adds the important behavioral detail that dry_run=true by default, which prevents accidental execution. However, it does not disclose other behavior like what happens on success, error handling, or required permissions.

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 sentence that front-loads the primary action and critical default. No wasted words; efficient and scannable.

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 3 parameters, no output schema, and minimal annotations. The description provides only the core purpose and a default, omitting return value, success/error handling, and prerequisites. Insufficient for an agent to fully understand usage without external knowledge.

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 descriptions cover all parameters (100% coverage). The description itself adds no additional meaning beyond restating the default dry_run value. Baseline of 3 is appropriate given high 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 the action ('Reopen') and the resource ('a closed epic'). It distinguishes the tool from siblings like 'close_epic' or 'reopen_issue' by specifying the resource type.

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 implies when to use (to reopen a closed epic) and highlights the dry_run default, but it does not explicitly explain when not to use, prerequisites (e.g., epic must be closed), or alternatives among siblings. Lacks explicit usage context.

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