export_distillates

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

With no annotations, the description must fully disclose behavior. It explains the marking of exported_at to prevent re-export and the default output path. However, it does not clarify whether the output file is overwritten or appended, error handling, or permission requirements. This leaves significant gaps for an agent.

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 sentences that are direct and informative. The first sentence states purpose, the second adds behavioral context, and the third provides a concrete default. No wasted 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 simplicity (2 optional params, output schema exists), the description covers the basics. However, it omits details like overwrite/append behavior, return format (output schema not explained), and response when no distillates match. Adequate but not comprehensive.

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 0%, so the description must add meaning. It explains min_vote as a threshold condition and mentions the default output path. However, it does not describe what happens when output_path is provided (e.g., relative vs absolute) or the expected format. Partial compensation for low schema coverage.

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: 'Write distillates with vote_sum >= min_vote to a jsonl bucket.' It specifies the condition for selection and the output destination. The name 'export_distillates' aligns with this purpose, and it is distinguishable from sibling tools like 'distill' and 'pending_distillates'.

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 for exporting distillates that meet a vote threshold, and mentions idempotency via the exported_at mark. However, it lacks explicit guidance on when to use this tool versus alternatives (e.g., export vs. direct retrieval) and no when-not-to-use scenarios.

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