delimit_gov_verify

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

With no annotations, description fully discloses side effects: require_premium gating, writes verification record (verdict, timestamp, repo, policy snapshot), and that it does not perform additional work. No contradictions.

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 headings and front-loaded purpose. Slightly lengthy due to detailed side effects, but every sentence earns its place. No redundant 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 role in a governance pipeline, the description covers prerequisites (pipeline step, license), side effects, and contrast with alternatives. Output schema exists, so no need to describe return format.

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 description coverage is 100%, so baseline is 3. Description does not add extra meaning beyond what the schema already provides for task_id and repo.

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?

Starts with a specific verb+resource: 'Attest that a governance task completed under policy'. Clearly distinguishes from siblings like delimit_gov_new_task, delimit_gov_run, and delimit_evidence_verify.

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?

Explicit 'When to use' and 'When NOT to use' sections. Names alternatives and provides contrast with sibling tools, including a sibling outside the gov family (delimit_evidence_verify).

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