delimit_external_pr_check

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

Discloses use of gh CLI, fail-closed verdict, 30-day window for merged PRs. No annotations available, so description carries burden; sufficiently transparent about behavior and return verdict.

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?

Front-loaded with purpose and usage instruction, then behavioral detail. Three concise sentences with no filler.

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?

Covers purpose, usage, and behavior. Does not mention 'state' parameter, but output schema likely handles return values. Minor gap but overall complete for a simple tool.

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 adds 'via gh CLI' context and recommends providing author, but otherwise does not enrich beyond 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?

States it checks for duplicate PRs in external repos before drafting. Implicitly distinguishes from siblings like delimit_collision_check by specifying 'external'. Could be more explicit about differentiation.

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 says 'Run BEFORE drafting' and for external repos. Provides clear context but no explicit when-not or alternatives.

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