memory_compress

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

With no annotations provided, the description fully shoulders the transparency burden. It explicitly states that compression is lossy, original entries are removed, and data is re-embedded. This disclosure is comprehensive 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?

The description is well-structured with clear sections (WHEN TO USE, EFFECTS). Every sentence adds value, and there is no redundancy. It is appropriately sized for a single-parameter tool.

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's simplicity (one param, no output schema), the description is complete. It covers purpose, usage conditions, and behavioral effects without any gaps. An agent can confidently select and invoke this tool.

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?

Only one parameter exists with 100% schema coverage. The description adds significant meaning beyond the schema by explaining each scope's effect and the requirement for epoch. This enriches the agent's understanding of how to select the appropriate scope.

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 purpose: compressing memory to reduce token usage and consolidate information. It identifies the specific resource ('memory') and action ('compress'), and distinguishes it from siblings like memory_forget or memory_retrieve.

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 provides explicit guidance for when to use each scope (working, session, epoch), including a prerequisite for epoch (at least 10 session summaries). While it doesn't explicitly state when not to use the tool, the sibling context and clear scope usage cover most decision-making needs.

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