delimit_release_validate

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

No annotations provided, so description carries full burden. Clearly states side effects: no side effects on success; on failure auto-chains three tools (evidence_collect, notify, ledger). Could add more about permissions or concurrency, but adequately covers key behavioral traits for a validation tool.

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?

Well-structured with clear sections (When to use, When NOT, Sibling contrast, Side effects). Each sentence is meaningful and earns its place. No fluff, front-loads key information.

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 output schema exists, description need not explain returns. Covers purpose, usage, side effects, sibling differentiation, and parameter context. Complete for a tool with 2 required params and no enums.

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?

Input schema covers 100% of parameters with descriptions. Description does not add extra meaning beyond the schema (only mentions environment/version implicitly). Baseline score of 3 is appropriate since schema already documents parameters fully.

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?

Clearly states 'Validate that a release is safe to ship' – specific verb (validate) and resource (release). Distinguishes from siblings by explicitly contrasting with delimit_release_plan (describes vs attests) and listing when-not-to-use alternatives (delimit_lint, 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?

Provides explicit when-to-use (gate between plan and rollout) and when-not-to-use (linting, runtime health). Mentions sibling contrast with delimit_release_plan, giving clear decision guidance.

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