reduce_snapshot

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

No annotations, so the description carries the full behavioral burden. It usefully discloses that the tool returns every partial snapshot plus a system prompt, and that save_snapshot clears partials, but it doesn't state whether reduce_snapshot itself has side effects, requires permissions, or what the partial payload contains.

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?

Four focused sentences, front-loaded with the tool's role, then return shape, merge rules, and next step. Some procedural detail could be trimmed, but each sentence carries actionable information.

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 no annotations, the description does a good job explaining the return value (partials + merge prompt) and the required save_snapshot follow-up. Missing details about partial structure or permissions are minor given the tool's narrow role.

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% for the single 'dir' parameter, so the description needn't restate it. The description adds no parameter syntax or format detail beyond the schema's absolute path description.

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?

States a specific verb and resource ('Reduce step of the concept-map build') and clarifies it returns partials plus a merge prompt, distinguishing it from the downstream save_snapshot step. It doesn't explicitly differentiate from get_snapshot, but the reduce/merge framing is clear.

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?

Explains the merge rules and the required follow-up call to save_snapshot, which implies when this step belongs in the pipeline. However, there is no explicit when-to-use/when-not guidance or comparison against sibling snapshot tools beyond the next-step reference.

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