consolidate_collection

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states that the tool consolidates memories into a summary or insight. It does not disclose whether the operation is destructive (e.g., deletes original memories), requires specific permissions, or modifies the collection state. The presence of a 'summarize_only' parameter in the schema implies mutation by default, but the description omits this crucial behavioral detail.

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 of 11 words with no superfluous content. It immediately states the action and the resource. It is front-loaded with the verb and noun, making it easy for an agent to parse quickly. Every word serves a purpose.

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?

Despite the simplicity of the tool (3 parameters, none nested), the description lacks completeness. It does not explain the return value (no output schema exists), the effect of 'summarize_only' on behavior, or what happens to existing memories after consolidation. Given that consolidation may be a mutating operation, the absence of these details leaves the agent guessing about side effects and expected outcomes.

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 coverage is 100%—all three parameters have descriptions in the JSON schema. The tool description adds no additional meaning beyond stating the overall operation. For example, the 'title' parameter is explained in the schema as 'Title for the consolidated memory (optional)', but the description does not clarify how or when the title is used. A baseline of 3 is appropriate since the schema already documents parameters adequately.

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: 'Consolidate all memories in a collection into a comprehensive summary or insight.' It uses a specific verb ('Consolidate') and resource ('memories in a collection'), and it differentiates from siblings like 'remember' (individual memory storage) and 'consolidate' (which may be more general or not collection-specific). The term 'comprehensive summary or insight' clarifies the output's nature.

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 is provided on when to use this tool versus alternatives. Siblings include 'consolidate', 'analyze', 'remember', and 'recall', but the description does not explain scenarios where consolidating a collection is preferable. There is no mention of prerequisites (e.g., collection must exist) or when to avoid using it (e.g., if individual memories are needed).

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