chat.compaction_knowledge

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

No annotations exist, so the description carries full responsibility for behavioral disclosure. It mentions returning a file path, which hints at possible snapshot creation, but does not state side effects, permissions, whether the operation is read-only, or the lifecycle of the returned path. The description adds only minimal context beyond the tool name.

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 front-loads the action and outcome. It is appropriately brief, though it could be slightly clearer about the nature of 'compaction knowledge metadata' without becoming verbose.

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?

With no output schema and a non-trivial purpose, the description leaves significant gaps: what a compaction snapshot is, how the returned path should be used, and how this tool relates to siblings like read_latest_knowledge or start_knowledge_index. The description provides only a high-level summary that is insufficient for confident invocation.

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 100%, so the parameter descriptions already document each parameter meaning. The tool description does not add any parameter-level detail beyond what the schema provides, making the baseline score of 3 appropriate.

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 uses a specific verb ('Collect') and identifies a concrete resource ('live compaction knowledge metadata'), and clearly states the outcome ('return an absolute file path for the compaction snapshot'). This distinguishes it from sibling tools focused on general knowledge search or sessions, though the term 'compaction knowledge' is not fully explained.

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 the many sibling knowledge tools. No context is provided about whether this is a read-only operation, whether it should be used before/after other compaction tools, or what conditions favor selecting it.

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