compress_history

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

The description explicitly discloses two behavioral effects: summarizing history and clearing Recent Actions. With no annotations, it adequately conveys the destructive nature (clearing actions).

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 that is direct and front-loaded. No extraneous words; every word contributes to understanding the tool's function.

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 parameter and no nested objects, the description covers the core action but omits explanation of the parameter's role. Output schema exists but is not shown; however, the description could be more complete.

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 only parameter, 'new_summary', is not explained in the description or the schema. The name hints at its purpose, but the description does not add any meaning, such as format or behavior (e.g., replacement vs. append).

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: summarizing history and clearing Recent Actions. It is distinct from sibling tools (log_action, set_core_objective, update_current_task) which have different purposes.

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?

No guidance on when to use this tool versus alternatives, nor any prerequisites or conditions. The description does not mention any exclusions or when not to use it.

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