release_plan

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

Declares 'Strictly read-only; nothing is touched' and lists all outputs (branches, MRs, tags, file edits, pipeline variables). With no annotations, the description fully covers behavioral traits.

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?

Two sentences, no unnecessary words. Front-loaded with purpose. Every sentence earns its place.

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?

Despite lacking parameter details, the description covers the core purpose, behavioral safety, and usage workflow. Given the presence of an output schema and the tool's role as a dry-run, the description is mostly complete. However, parameter documentation gap reduces completeness.

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 has 4 parameters with 0% description coverage. The description does not explain any parameter meaning (e.g., coordinate, env, inputs). It relies on the assumption that parameters match release_start, which is not stated explicitly. This is a significant gap.

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?

Description clearly states it is a dry-run of release_start, listing exactly what would be created (branches, MRs, tags, etc.). It distinguishes itself from siblings by explicitly contrasting with release_start.

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?

Explicitly instructs to call this before release_start with the same arguments, show the plan to the user, and only call release_start after confirmation. This is exemplary usage guidance.

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