distill_logs

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

With no annotations, the description partially discloses behavior by mentioning what is preserved (startup, shutdown, errors). However, it does not specify if the tool mutates the input, requires permissions, or what happens to omitted content beyond 'omitting'. More detail on side effects would improve transparency.

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 a single concise sentence (22 words) that front-loads the action. It is efficient, though it omits many details that could be included without becoming overly long.

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 tool has 6 parameters (including complex ones like error_patterns array and token_budget) and no output schema, the description is insufficient. It does not explain the compression algorithm, return format, or how parameters interact, leaving significant gaps for an agent.

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 description coverage is 0%, so the description must compensate. It does not explain any parameter meanings; parameters like keep_head, keep_tail, error_patterns, dedup, and token_budget are only inferable from their names. The description lacks any parameter-specific guidance.

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 it filters and compresses raw logs by preserving startup, shutdown, and error content while omitting repetitive messages. This distinct purpose differentiates it from sibling tools like distill_conversation or distill_json, which handle different data types.

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 log compression, but does not explicitly state when to use this tool versus alternatives like distill_conversation. There are no usage exclusions or alternative tool mentions, leaving the agent to infer appropriate contexts.

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