delimit_release_plan

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

Discloses side effects as 'read-only on git/repo state', gated by require_premium, and internal call to backends.tools_infra.release_plan. With no annotations provided, this adds necessary behavioral context, though could elaborate on 'read-only' implications.

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?

Concise single paragraph with front-loaded purpose, clear usage guidelines, and transparency info. No extraneous text.

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's complexity (4 optional params, output schema present), the description covers purpose, usage, side effects, and access requirements comprehensively. Completeness is high.

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 coverage is 100%, so baseline 3. Description adds no extra parameter info beyond what the schema already provides.

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 explicitly states 'Generate a release plan from git history (Pro)', with a specific verb and resource. It contrasts with siblings (delimit_release_validate, delimit_deploy_publish, delimit_deploy_plan) to differentiate.

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?

Clearly states when to use ('ahead of cutting a release') and when not to use ('to validate readiness' or 'to ship code'), naming alternative tools. Also contrasts with delimit_deploy_plan for single-app deploys.

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