backlog_consolidation_candidates

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

No annotations exist, so the description must disclose behavioral traits. While it implies a read operation ('list'), it does not explicitly state safety characteristics (e.g., read-only, no side effects). The workflow mentions future deletions via backlog_forget, but the tool itself is not clarified. A middle score is warranted as the description adds context but is not fully transparent.

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 paragraph but well-organized with numbered workflow steps. It efficiently conveys necessary information without redundancy. Slightly more structure (e.g., bullet points) could improve scanability, but it remains concise.

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 complexity of the tool and its role in a multi-step workflow, the description fully explains what it returns (clusters/bundles of memories), how to use it, and the meaning of parameters in context. No output schema exists, but the description implies output structure sufficiently.

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%, so baseline is 3. The description adds significant value by explaining how parameters like min_count, min_demand, and min_age_days determine ripeness, and by providing context on bundle structure. This goes well beyond the schema descriptions.

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 begins with a clear verb and resource: 'List clusters of episodic memories that are ripe for consolidation'. It specifies the exact purpose and distinguishes from siblings by referencing the consolidation workflow and related tools.

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 an explicit step-by-step consolidator workflow (1-4), telling the agent when to call this tool, how to process results, and which sibling tools to use subsequently. This is exemplary usage guidance.

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