delimit_external_pr_check

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

With no annotations, the description describes behavior: uses gh CLI, returns 'fail-closed verdict', and criteria for duplicate. It misses potential error handling details but provides sufficient transparency for typical use.

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?

Extremely concise: three sentences front-loaded with purpose, then behavioral details. No redundant words.

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 moderate complexity and existence of output schema, the description covers purpose, usage context, and behavior completely. No gaps remain.

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 is 3. The description adds minimal extra meaning, reinforcing 'repo' as external and 'author' as recommended filter, but mostly restates schema.

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?

The description clearly states the tool's purpose: 'Pre-PR duplicate guard for external repos.' It specifies the verb 'run BEFORE drafting' and distinguishes itself from siblings by focusing on duplicate checking for external repos. There is no ambiguity.

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?

The description explicitly says 'Run BEFORE drafting' and explains the scenario when it returns 'duplicate' to stop drafting. However, it does not mention when not to use it or alternative tools, but the context is clear.

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