Sync Media Files

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing. It does not say whether the sync is one-way or bidirectional, whether destination files not present in source are deleted, whether existing files are overwritten, or whether a dry-run exists — all critical for a potentially destructive operation.

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?

A single five-word sentence with no padding and the scope stated up front, so structure is fine. However, it is under-specified rather than truly concise — the brevity reflects missing content, not efficiency.

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 not be explained. But for a two-parameter mutation-style tool with zero annotation coverage, zero parameter documentation, and no behavioral detail, the definition leaves an agent unable to call it correctly or safely.

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 0%, so the description must compensate, and it does not. It gestures at 'paths' but adds no format, path-style, stream-wrapper, or trailing-slash semantics for source_path and destination_path.

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?

It states a verb (sync) and a resource (media files) plus a scope (between paths), so the purpose is inferable. But it is essentially a restatement of the name and title, and gives no differentiation from siblings that also touch media (upload_media, fix_media_references, media_bulk_import).

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 when-to-use guidance, no prerequisites, no exclusions, and no pointer to any alternative tool. The agent must guess whether this is for local filesystem moves, remote stream wrappers, or Drupal media entities.

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