delimit_outreach_loop_tick

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

No annotations provided, so description carries full burden. Details side effects: reads ledger, network reads, writes new intel-class LEDs, dispatches substantive tasks. Also mentions kill switches (env var and sentinel file), per-tick caps, and intentional limits.

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 sections (main sentence, when to use, when not, sibling contrast, side effects). Front-loaded, every sentence earns its place, 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?

Complete for this tool: covers purpose, usage, parameters, side effects, kill switches. Output schema exists so return values not needed. No gaps.

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?

100% schema coverage, baseline 3. Description adds extra context beyond schema: explains 'max_dispatch' that targets beyond cap still file intel LEDs but not dispatched, and 'max_monitor' as monitor-call cap. Adds value.

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 'Run one tick of the autonomous github-outreach loop' (specific verb+resource). Differentiates from siblings like delimit_social_target (broader platform set) and delimit_sensor_github_issue (single issue).

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 states when to use (external scheduler or manual cycle) and when not (backfill of stale items due to per-tick caps). Provides correct alternative pattern (multiple ticks at scheduler interval).

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