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

Annotations declare readOnlyHint=false and destructiveHint=false, so safety is covered. The description still adds real context beyond them: unchanged sections are skipped unless force is set, and it feeds the WordPress export (explaining the consequence of running it and what it prevents — fallback templates). It does not describe the response or how long a run takes.

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 scoping condition is front-loaded in the opening clause, and every sentence contributes (scope, effect, sibling relationship, force semantics). It is a single dense paragraph and could break up more cleanly, but there is no filler.

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 two-parameter mutation with no output schema, the description covers when to run it, what it changes, why it matters for export, and how force alters behavior. Only the shape of the result (progress/success reporting) is left implicit.

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 0%, so the description must carry parameter meaning, and it does for the non-obvious one: force overrides the skip-unchanged behavior. projectId is not described, but its role is unambiguous from the 'for a project' framing and the name.

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 states a concrete operation: populating Label Studio with each imported section's Elementor/Gutenberg code, CSS, scripts, copy and images. It explicitly scopes this to imported projects and distinguishes it from the sibling uichemy_mark_exported, though the prose is dense and the tool name ('sync_builders') alone would not convey this.

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?

It names the exact precondition (projects imported from code, not new template-built projects) and an explicit exclusion ('new projects are built from UiChemy templates only'). It also routes the agent relative to the sibling: uichemy_mark_exported triggers this too, but calling this directly lets you verify first.

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