delimit_github_scan

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

No annotations are provided, so the description carries full burden. It discloses 'Side effects: read-only network' and details a required tool chaining rule after scanning, which gives clear behavioral expectations for the AI agent.

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?

The description is well-structured with clear sections (purpose, usage, siblings, side effects, tool chain). It is somewhat verbose but every sentence adds value, and the most important information is front-loaded.

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 complexity (multi-cadence scanning, post-processing requirements) and presence of an output schema, the description covers all necessary context: purpose, when/not to use, sibling differentiation, side effects, and mandatory chaining instructions.

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 clear descriptions for both parameters (cadence and limit). The description does not add substantial new meaning beyond the schema, but it does mention cadence values briefly. Baseline of 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?

The description clearly states the tool's purpose: 'Scan GitHub for adoption leads, competitive intel, repo health'. It uses a specific verb (scan) and resource (GitHub), and differentiates from siblings by naming delimit_sensor_github_issue and delimit_tracker_sync.

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 guidance (at configured cadence: pulse, hunter, deep) and when-NOT-to-use (monitor one issue or pull issues), with references to alternative tools. The sibling contrast section further clarifies usage boundaries.

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