nexo_consolidate

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

The description hints at mutable behavior (promote, process, dream, consolidate) but does not disclose side effects, whether it is destructive, required permissions, or rate limits. With no annotations, the description carries the full burden and falls short.

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 too brief given the tool's apparent complexity. It sacrifices necessary information for brevity, resulting in under-specification.

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 lack of output schema, zero annotation coverage, and multiple sibling tools, the description is severely incomplete. It does not explain what the parameters do, what the consolidation process entails, or how it relates to other cognitive tools.

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 input schema has three parameters (max_insights, threshold, dry_run) with no description coverage in the schema and no explanation in the tool description. The description adds zero meaning beyond the parameter names and defaults.

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 specifies the action as running NEXO memory consolidation, listing sub-actions (promote, process quarantine, dream, consolidate). This gives a clear verb and resource, but it does not fully distinguish from similar sibling tools that handle individual steps like nexo_cognitive_quarantine_promote or nexo_cognitive_quarantine_process.

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 the many sibling tools that perform individual operations. The description lacks any context about preferred scenarios, prerequisites, or alternatives.

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