harness_sync_design_system

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

The description details the actions taken (connect, pull, store, queue), providing reasonable transparency. However, it does not discuss side effects (e.g., overwrite behavior) or error conditions, which would be beneficial given no annotations.

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 two sentences: first captures core functionality, second provides usage context. No redundant information; extremely concise.

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 description covers the main workflow and usage context adequately. It could mention output or follow-up, but the sibling list partially fills that gap. Reasonably complete for a sync tool.

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 input schema covers 100% of parameters with clear descriptions. The tool description does not add additional meaning beyond the schema, meeting the baseline.

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 action (sync design system from external server), describes the mechanism (connects to Design MCP server, pulls tokens and rules, stores tokens, queues rules), and distinguishes from a sibling tool (harness_set_design_tokens). It is specific and actionable.

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 second sentence explicitly provides when-to-use and when-not-to-use guidance, naming the alternative harness_set_design_tokens. This helps the agent choose correctly.

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