palinode_consolidate

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

The description goes beyond annotations by recommending dry_run=true for MCP invocation and noting the tool is destructive (via the schema parameter text). It discloses that dry_run previews operations without writing changes, adding safety context. However, it does not detail what consolidation actually does (e.g., merges, deletes, rewrites) or what side effects occur when applied, leaving some behavioral ambiguity.

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 consists of two concise sentences, front-loaded with the main action and immediately providing the key preview guidance. There is no redundant or filler wording. It is appropriately sized for a tool with a well-documented schema, and every sentence earns its place.

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?

The tool has no output schema, and the description does not explain what a consolidation pass produces (e.g., a report, applied changes, or a diff). It relies on the schema for parameter context and the annotations for destructive safety, but for a destructive operation, more detail about the actual consolidation operations and consequences would be expected. It is minimally adequate but has clear gaps.

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%, with each parameter (dry_run, nightly, sources) having helpful descriptions that explain defaults and usage. The tool description itself adds no new parameter information beyond the schema, so the baseline of 3 applies. It confirms the dry_run preview behavior but does not enrich beyond what schema already provides.

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 states a specific action ('Run a manual knowledge consolidation pass') with a clear resource ('knowledge consolidation'). The word 'manual' helps distinguish it from automatic passes, and the phrase distinguishes it from sibling tools like palinode_dedup_suggest or palinode_archive_expired. However, 'consolidation pass' is jargon and not fully explained, slightly reducing clarity.

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 implies this tool is for manually triggering consolidation when desired, and the dry_run recommendation provides a usage tip for safe previewing. But it does not explicitly state when to use this tool over alternatives (e.g., automatic consolidation, dedup_suggest, archive_expired), nor any exclusions or conditions. Usage context is only implied, not explicit.

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