sync_to_files

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

With no annotations, the description carries the full burden and does well: it discloses the write target, that only the 'managed section' is touched (implying other file content is preserved), and the observable downstream effects (shared with teammates and non-Aether tools, visible in code review). It leaves one real ambiguity — whether the tool itself commits or merely writes files that are later committed — and says nothing about idempotency or overwrite behavior.

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?

Two sentences, front-loaded with the action and target, followed by the rationale and the trigger condition. No filler or restated name/title; every clause adds either scope, justification, or the call condition.

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?

An output schema exists, so return values need no explanation, and with zero parameters the remaining burden is behavioral. The description covers destination, audience, and trigger, but does not resolve whether the tool performs the commit or whether repeated calls are safe, which are the two things an agent would still want before invoking it.

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 clarify beyond the schema. The baseline for a no-argument tool applies, and the description correctly spends no words on parameter explanation.

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 verb and destination ('Write this project's current memories into the managed section of AGENTS.md / CLAUDE.md'), which is materially different from siblings like remember (writes to the cache) or recall (reads). An agent can distinguish this persistence/sync action from the rest of the family without opening any schema.

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?

It gives explicit trigger conditions: 'Call it when the user asks, or after a batch of new memories.' That is clear when-to-use guidance, though it names no alternative or exclusion (e.g. it does not say what to use instead when only a single memory changed).

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