cleanup_task_history

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

The description implies a destructive action ('remove') but provides no detail on consequences, reversibility, impact on ongoing tasks, or safety. With no annotations, the description carries the full burden, and it fails to disclose potential side effects or prerequisites.

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 sentence, which is concise and front-loaded with the core action. However, it is too sparse, omitting essential context about the parameter and behavioral implications. It is not verbose but sacrifices completeness.

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 one optional parameter and no output schema, the description should at least explain the meaning of 'old' and the parameter's role. It also does not address the effect on task-related tools (e.g., task_status, task_result). The description is incomplete for an agent to use it 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 one parameter, older_than_seconds, with no description (coverage 0%). The tool description does not mention this parameter at all, nor does it clarify how 'old' is determined. The meaning of the parameter is left entirely to its name, which is insufficient.

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 action 'Remove old tasks from history' with a specific resource (tasks) and distinguishes it from storage-related siblings like storage_cleanup. However, the term 'old' is undefined, leaving ambiguity about the criteria without consulting the parameter.

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 context on appropriate invocation timing (e.g., periodic cleanup) or conditions. The description does not mention any related tools or scenarios.

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