trigger_user_sync

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

Annotations already declare destructiveHint=true, readOnlyHint=false and idempotentHint=false, so the description's added value is the precondition (only works when the AI agent is not busy) and the disclosure that on-disk source files are mutated. It stops short of saying whether a failed run leaves partial edits, which matters for a non-idempotent destructive tool.

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 labelled structure (when to use / when not to use / side effects) is scannable and front-loaded with the core action. There is mild redundancy in restating 'applies all queued edits (dimension + color)' a second time and in the Returns block, which duplicates the output schema.

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 zero-parameter, non-idempotent, destructive tool the description covers intent, precondition, side effect and result shape, and an output schema plus annotations carry the rest. The remaining gap is recovery guidance – nothing points at rollback_last if applied edits turn out to be wrong.

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 tool takes no parameters, so there is nothing for the description to disambiguate – the baseline applies. The only semantic detail given, that the queued edits cover dimensions and colors, is useful framing but not a parameter concern.

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 names a concrete operation (trigger user_sync on the Bridge Server) and states its effect: applying queued dimension and color edits to source files. That is enough to separate it from siblings such as get_sync_status or approve_file_changes, though those siblings are never named explicitly.

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 gives an explicit 'When to use' rule (flush and apply pending queued edits from the Android device) and an explicit 'When NOT to use' rule (the agent_busy lock, or the agent actively editing source files). The reader needs no inference to decide whether to call it.

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