Save now

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

Annotations already declare the safety profile (write, idempotent, non-destructive). The description adds meaningful context beyond them: it flushes all *pending* changes, is immediate, and is redundant with automatic saving. It doesn't describe failure modes (e.g., disk errors), but for a zero-argument flush tool this is solid added value.

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?

A single sentence with zero waste; the action is front-loaded and the caveat about automatic saving is compactly bracketed rather than given its own sentence.

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?

For a no-parameter, no-output-schema tool, the description covers the essential behavior and the key caveat that saving is already automatic. Minor gap: no indication of what happens on success/failure or whether it blocks, but little is required here.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. Baseline of 4 applies per the scoring rules.

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: 'Write all pending changes to the project folder immediately.' An agent immediately knows this is a manual save/flush operation, distinct from the node/link/zone CRUD siblings. It does not explicitly name a sibling to contrast against, but none of the siblings overlap in function.

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?

'immediately' plus the parenthetical '(hive also saves automatically)' tells the agent both when to call it (to force an immediate flush) and that it is usually unnecessary because auto-save runs. No explicit alternative or exclusion is named, but the when/when-not context is clear.

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