Delimit Digest

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

Beyond the annotations, the description discloses concrete side effects: action='run' writes markdown and JSON to ~/.delimit/digest/, email requires DELIMIT_DIGEST_EMAIL=true as a pipeline gate, and action='latest' is read-only. This is exactly the behavioral context an agent needs.

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?

The description is organized with clear sections: purpose, when to use, when not to use, sibling contrast, and side effects. Every sentence carries useful information, and the most important purpose is front-loaded.

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 tool with four optional parameters, a full input schema, an output schema, and rich annotations, the description covers all non-obvious runtime behavior: file writes, email gating, read-only actions, and route selection against sibling tools. Nothing essential is missing.

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?

The input schema already covers all four parameters at 100%, so the baseline is 3. The description adds meaningful semantics by explaining the action='run' vs 'latest' behavior, the email env gate, and the windowed-rollup nature that relates to window_hours. This pushes it above baseline.

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 states a specific verb and resource ('Generate a structured daily digest of loop activity') and explicitly contrasts it with delimit_notify and delimit_notify_inbox. This makes the tool's identity unmistakable even among a very large sibling set.

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?

Includes explicit 'When to use' and 'When NOT to use' guidance, names the exact alternative tools, and adds a sibling contrast sentence. An agent can reliably select this tool versus delimit_notify without further inference.

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