sync

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

With no annotations provided, the description fully carries the burden of behavioral disclosure. It reveals important behaviors: backing up the child version to .sync-backup/ before overwriting, updating .source.json, requiring sourceWorkspace on first distribution, and rejecting default-skills. This is rich, actionable behavioral context beyond the schema.

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 compact and front-loaded, using four sentences to convey purpose, behavior, parameter conditionality, and exclusions. Every sentence earns its place with no redundancy or 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?

Given the tool's moderate complexity, no output schema, and helpful parameter schema, the description covers all essential aspects: what it does, how it behaves, when to use the optional parameter, and what it rejects. It is complete enough for an agent to correctly invoke the 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?

Schema coverage is 100%, so the baseline is 3. The description adds value by clarifying that 'skill' is the directory name and 'workspaces' are child workspace slugs, and it reinforces the conditional requirement of sourceWorkspace for first-time distribution. This exceeds the baseline by providing operational context not fully explicit in 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 a specific action: pushing an entire skill directory from a parent workspace to one or more child workspaces. It distinguishes this tool from siblings by focusing on the sync/push operation and explicitly mentioning the backup and overwrite behavior.

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 description provides clear usage context: it specifies the sourceWorkspace parameter is required for first-time distribution, and it notes automatic rejection of default-skills. It does not explicitly name alternative tools or exclusion cases, but the context is sufficient for typical use.

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