delimit_vendor_news_scan

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

No annotations provided, but description covers side effects: gated by require_premium, wraps sensor+drafter, and details dry_run behavior (cache-friendly, skips JSONL log and drafter). Comprehensive disclosure.

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 sections: main action, usage guidelines, sibling contrast, side effects. Concise and front-loaded with essential information.

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 parameter thoroughly. Output schema exists, so return values need not be explained. Complete for an ad-hoc scan tool with good annotations (even though annotations are absent, description compensates fully).

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?

Single parameter dry_run has schema description, but description adds significant value: explains cache-friendly polling, skipping JSONL log write, drafter, queue, and rate-cap consumption.

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 it scans watchlisted vendor accounts and auto-drafts riffs. It uses specific verbs and resources, and distinguishes itself from siblings like delimit_vendor_news_draft and delimit_vendor_news_health.

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 (ad-hoc execution) and when not to use (single tweet or subsystem health), and provides sibling contrast with clear alternatives.

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