sync_directory

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

With no annotations present, the description carries the full burden of behavioral disclosure. 'Manually sync' implies a state-changing operation with potential data overwriting, but no side effects, permissions, rate limits, or impact considerations are mentioned. The description is too thin to convey the operational risks.

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 single sentence is concise, front-loaded with the primary action, and avoids redundancy. It earns its place by stating the tool's core purpose, though it lacks supplementary details that would make it more helpful.

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?

Despite a simple schema and existing output schema, the description omits essential operational context. It fails to explain what syncing does, whether it is destructive, when to use it, or how it relates to sync_all_directories. This leaves significant gaps for an agent to safely invoke the tool.

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 provides 100% coverage with clear descriptions for both parameters, including examples for 'directory' and a note for 'scope'. The description adds no additional parameter semantics beyond what the schema already offers, 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 the action (sync), the resource (a specific directory), and the source (from API). It directly distinguishes itself from the sibling 'sync_all_directories' by emphasizing 'specific', making the purpose unambiguous.

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 guidance is provided on when to use this tool versus alternatives like sync_all_directories. There is no mention of prerequisites, exclusions, or scenarios where this tool is preferred. The context is purely implied by the tool's name and description.

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