delimit_release_validate

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

No annotations provided, but description fully discloses side effects: on success no side effects, on failure auto-chains three specific tools. This gives agents essential behavioral expectations.

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?

Compact yet thorough: organized into clear sections (purpose, when to use/not, sibling contrast, side effects). Every sentence adds value, no fluff.

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 existence of an output schema and full parameter schema, the description covers all critical aspects: pipeline role, auto-chaining behavior, and differentiation from related tools. Sufficient for correct agent selection and invocation.

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% with both parameters (environment, version) well-described. Description does not add extra parameter details, but baseline 3 is appropriate since schema already provides sufficient semantics.

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?

Clear verb+resource: 'Validate that a release is safe to ship.' Distinguishes from siblings by stating it's the gate between delimit_release_plan and rollout, and contrasts with delimit_lint and delimit_obs_status.

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 states when to use (as gate between plan and rollout) and when not (for linting or runtime health). Provides sibling contrast, clarifying that delimit_release_plan describes what would ship, while this attests safety.

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