export_distillates

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

The description discloses an important non-obvious behavior: items are marked exported_at so they won't be re-exported on subsequent calls. This goes beyond the annotations, which only indicate the operation is not read-only, not idempotent, and not destructive, and gives the agent a realistic expectation of state changes.

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?

Three compact sentences, each carrying necessary information: the operation, the deduplication behavior, and the default destination. The key action is front-loaded, and there is 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 tool with only two optional parameters and an output schema, the description covers the essential invocation details. Minor gaps remain, such as whether the output file is overwritten or appended, but the description is sufficient for correct selection and basic usage.

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 description adds meaning to both parameters: min_vote is tied to the vote_sum filter, and the default output path is explicitly stated. This complements the schema, where output_path defaults to an empty string and min_vote defaults to 1, by explaining what those defaults actually mean.

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 action ('Write distillates'), the target format ('jsonl bucket'), the selection criterion ('vote_sum >= min_vote'), and the key side effect (marking exported_at). This clearly distinguishes it from siblings like pending_distillates or distill.

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 intended use is clear: call this to export qualifying distillates to a JSONL file, and the min_vote threshold defines exactly which items are eligible. It does not explicitly name alternatives or exclusions, but the context is unambiguous enough for an agent to select it appropriately.

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