faf_bi_sync

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

Annotations indicate write operations (readOnlyHint=false) and non-destructive (destructiveHint=false). The description adds behavioral context like version info and additional sync targets, but does not disclose conflict resolution details beyond the 'force' parameter, file locking, or side effects.

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 very short (two sentences) and front-loads the core purpose. Efficient use of words, though it could benefit from slightly more structure or bullet points.

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 tool with 8 parameters and no output schema, the description omits critical context like overall behavior (one-time vs continuous sync), prerequisites, return format, and error scenarios. Incomplete for effective agent reasoning.

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% with clear descriptions for each parameter. The tool description adds no additional parameter explanations, so the baseline score 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 it performs a bi-directional sync between project.faf and CLAUDE.md, listing additional target formats. The verb 'sync' and resource 'project.faf and CLAUDE.md' are specific. It does not explicitly differentiate from sibling faf_sync, but the name implies distinction.

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 lacks any guidance on when to use this tool versus alternatives like faf_sync. No when-to-use or when-not-to-use hints are provided, leaving the agent to infer usage context.

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