delimit_social_daemon

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

With no annotations, the description carries the full burden. It discloses periodic scanning, deduplication, and email output, but does not mention side effects, resource usage, or potential data loss on stop. Lacks full transparency for a daemon control tool.

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?

Two concise sentences that front-load the core purpose and efficiently describe behavior. No redundant or unnecessary 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?

Given the presence of an output schema, the description does not need to detail return values. It provides sufficient context about daemon behavior for an agent to understand its function, though it could hint at the response format for 'status'.

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 the action parameter already described. The tool description adds no extra meaning beyond the schema's enumeration of 'start', 'stop', and 'status'. Baseline score 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 explicitly states 'Control the social sensing daemon' and details its periodic behavior (every 15 minutes), deduplication, and email generation. It clearly distinguishes from sibling tools like delimit_reddit_scan by focusing on daemon operation rather than one-time scans.

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?

The description implies usage by listing actions (start, stop, status) but does not explicitly state when to use this tool versus alternatives like delimit_reddit_scan or other social tools. No when-not-to-use guidance is provided.

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