delimit_vendor_news_health

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

Discloses side effects: 'read-only.' Lists exactly what it reads (crontab, sensor JSONL log, tweet queue, etc.). Mentions gating: 'Gated by require_premium.' No annotations exist, so description fully covers behavior.

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 for when to use, when not to, sibling contrast, side effects, args, and returns. Every sentence adds value, no filler. Appropriately concise for a zero-param tool.

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?

Completely covers a simple health-check tool: no parameters, clear return dict structure with specific keys. Output schema exists but description provides helpful human-readable summary.

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?

No parameters in schema. Baseline of 4 is appropriate since there is nothing to describe; the description does not need to add param info.

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 'Health check for the vendor-news riff system' – specific verb ('health check') and resource. Distinguishes from siblings explicitly: 'delimit_vendor_news_draft writes one riff; delimit_social_daemon controls the broader sensing daemon; this is the vendor-news subsystem 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?

Provides explicit 'When to use' and 'When NOT to use' sections with concrete examples ('is the cron firing? are drafts landing?') and alternative tool names. No ambiguity.

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