sync_ui_data

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

No annotations provided. The description adds behavioral context: data storage location, default apply-on-next-startup behavior, force/verbose options. Does not disclose overwrite or permission details, but covers key operational traits.

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?

Two sentences, no redundancy. First sentence states primary action, second sentence adds essential context (storage and timing). Efficiently front-loaded.

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 simple tool with no output schema and two boolean params, the description provides adequate context: data flow, default behavior, and sync options. Could mention overwrite policy but overall 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 coverage is 100% with detailed descriptions. The description reiterates force (ignore version) and verbose (detailed logs) but does not add significant new semantics beyond the schema.

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 syncs UI/UX data to local cache from npm package uipro-cli, with specific sources (npm) and destination (~/.mcp-probe-kit/ui-ux-data/). This distinguishes it from siblings like ui_design_system and ui_search.

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?

Implied usage for syncing data, but no explicit when-to-use or when-not-to-use guidance. No alternatives are mentioned, though the siblings list suggests other UI tools.

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