delimit_external_pr_check

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

Describes using gh CLI to list PRs, returning a fail-closed verdict based on open PRs or recent merges. No annotations exist, so description carries full burden; it adequately covers behavioral traits.

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?

Very concise: two sentences with a follow-up. Front-loaded with purpose and usage timing. No wasted 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?

Covers purpose, usage, behavior, and verdict logic. Given the tool's low complexity and existence of output schema, it is fully informative for an agent.

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 good descriptions; the description reiterates 'repo' and 'author' but does not add new meaning beyond schema. Baseline 3 is appropriate.

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 it is a 'Pre-PR duplicate guard for external repos', explaining it lists existing PRs and returns a verdict. Distinguishes itself from siblings by focusing on external PR duplication detection.

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 instructs 'Run BEFORE drafting', providing clear timing. Does not mention when not to use or alternatives, but context implies use for external repos only.

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