distill_journal

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

The description clearly explains the pipeline steps (read, group, write, advance) and declares idempotency. No annotations exist, so the description fully covers behavior. It could mention potential side effects like advancing the watermark, but it already does implicitly.

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 very concise with two clear sentences. It is front-loaded with the action. However, it misses parameter details, which could be added without losing conciseness.

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 no output schema and 0% parameter description coverage, the description leaves gaps in understanding what is returned and how parameters work. While the pipeline steps are clear, an agent would need extra context to use parameters 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?

The input schema has two parameters (project_slug, max_events) with 0% description coverage. The description provides no explanation of what these parameters mean or how they affect behavior. For example, 'max_events' likely caps the number of events processed, but this is not stated.

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 the tool's action: reading raw events, grouping by topic, writing markdown entries, and advancing a high-water mark. The term 'distillation pipeline' and the specific steps differentiate it from sibling journal tools like journal_append or housekeep_journal.

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 it is a batch process that is idempotent, which guides usage for repeated runs. However, it does not explicitly state when to use this versus other journal tools (e.g., journal_note for manual entries), nor does it mention prerequisites or when not to use it.

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