Delimit Social Daemon

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

Annotations only provide readOnlyHint=false and destructiveHint=false, but the description adds substantive behavioral context: start/stop mutate daemon state, the daemon autonomously scans/deduplicates and emits HTML draft emails, and it maps to ai.social_daemon.{start_daemon, stop_daemon, get_daemon_status}. This goes well beyond the annotation flags and does not contradict them.

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?

Every labeled section earns its place: when-to-use, when-not-to-use, sibling contrast, side effects, and internal method mapping. Despite being detailed, the description is scannable, front-loaded, and contains no filler.

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?

For a one-parameter tool with an output schema, this is complete: action semantics are clear, exclusions are explicit, side effects are disclosed, and sibling tools are referenced. An agent has everything needed to select and invoke it correctly.

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%, so the action parameter is already documented; the description still adds value by tying 'status' to inspection and noting that 'start'/'stop' mutate daemon state. The internal method mapping provides extra semantic grounding for the parameter values.

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?

Description opens with a specific verb and resource, 'Control the social sensing daemon (Pro)', and enumerates the supported start/stop/inspect operations within an explicit every-15-min scanning scope. It also differentiates itself from delimit_social_target as the one-shot alternative, so an agent can tell them apart without opening the schema.

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?

Contains explicit 'When to use' and 'When NOT to use' sections that name delimit_social_target for one-shot scans and delimit_notify_inbox for inbox reads. The sibling-contrast line further reinforces the long-running daemon versus one-shot boundary, leaving no ambiguity about when to invoke this tool.

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