faf_sync

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

Annotations indicate non-readOnly and non-destructive, but the description adds little beyond stating 'bi-directional context.' It does not explain overwriting behavior, conflict resolution, or whether the tool modifies both files equally. The emoji adds no informational 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?

The description is a single sentence that is front-loaded with the core action. It is concise but uses an informal tone with emojis, which is acceptable. No unnecessary words, though some may find it under-specified.

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 tool has no output schema and only one optional parameter, the description is too brief to be contextually complete. It does not specify what happens if 'path' is omitted, whether the sync is automatic, or what the result looks like. An agent may lack confidence in invoking the tool correctly.

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 already provides a clear description for 'path' (sets session context). The tool's description does not reference the parameter or add any additional meaning beyond the schema. Since schema coverage is 100%, a baseline of 3 is appropriate.

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 clearly states the tool syncs 'project.faf' with 'CLAUDE.md' and specifies bi-directional context. This distinguishes it from sibling tools like faf_init or faf_write, which have different purposes.

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 explicit guidance on when to use this tool versus alternatives like faf_init or faf_bi_sync. The description implies usage for syncing DNA files but does not provide context for when this action is appropriate or what prerequisites exist.

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