clean_container_log

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

No annotations are provided, so the description carries the full behavioral burden. It says nothing about whether the operation is destructive, what gets removed, whether it is reversible, required permissions, or side effects. This is a severe gap for a mutation tool.

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?

At three words, the description is not concise so much as under-specified. It front-loads no useful constraints, conditions, or warnings, and every sentence that would earn its place is absent.

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 likely destructive maintenance operation with no annotations, no parameter documentation, and no output schema, the description is completely inadequate. An agent would lack essential information to invoke it safely or 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 schema has 0% description coverage for its single required `id` parameter, and the description provides no meaning for it. The agent cannot tell whether `id` refers to a container ID, log ID, or something else, and must rely entirely on the bare schema.

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 is essentially the tool name restated in title case ('Clean container log'), with no additional clarification. While it names a resource and an action, it does not explain what 'clean' means (delete, truncate, rotate) or distinguish it from siblings like `get_container_logs` or `clean_compose_log`.

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?

There is no guidance on when to use this tool versus alternatives, nor any mention of prerequisites or related log-retrieval tools. The description simply names the operation, leaving the agent to infer context entirely.

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