manage_sync

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

With no annotations, the description must carry the burden of behavioral disclosure. It reveals key side effects: write_file 'apply[ies] it to the Studio script' and export_scripts 'dump[s]' files to disk. However, it does not mention overwrite behavior, permission requirements, or error conditions, leaving some behavioral ambiguity.

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 dense sentence with a colon and semicolon-separated list. It is efficient, with no filler, and each action gets a brief parenthetical. However, it is somewhat run-on and could benefit from bullet points for easier scanning.

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?

The tool has 7 parameters and 8 actions; the description covers all actions and hints at return values (e.g., 'place + sync dir + last export', 'last export stats'). It does not distinguish status from status_current_place, and with no output schema, exact return formats are only partially implied, but overall it is reasonably complete.

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 description coverage is 86% (high), so the baseline is 3. The description adds significant value by explaining what each action parameter does (e.g., 'history (recent sync operations)', 'directions (get or set per-type sync directions)'), going beyond the bare schema descriptions and enum values.

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's purpose: 'Sync between Studio and the local filesystem.' It then enumerates all eight actions with specific explanations, making it easy to distinguish from siblings like manage_scripts (script management) and execute_luau (code execution).

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 implies usage through its opening phrase and details the behavior of each action (e.g., 'export_scripts' dumps scripts to disk, 'write_file' writes and applies to Studio). It does not explicitly name alternatives or exclusions, but the action list provides sufficient context for most use cases.

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