sync_skills

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

The description mentions 'optional git warnings' but does not elaborate on the sync behavior (e.g., whether it overwrites or merges), potential destructive actions, or reversibility. Given no annotations, the description should disclose more behavioral 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?

The description is a single sentence, which is concise but overly terse. It lacks structural elements like bullet points or sections. While not verbose, it sacrifices completeness for brevity.

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 complexity (4 parameters, 0% schema coverage, no annotations) and existence of an output schema, the description is too sparse. It does not mention return values, prerequisites, or side effects, leaving the agent with incomplete context.

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?

With 0% schema description coverage, the description must compensate but fails to explain any of the four parameters (targets, drift_decision, check_gitignore, skill_id_or_name). The drift_decision enum is not explained. The agent lacks essential information to use the tool.

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 verb 'synchronize', the resource 'canonical Agent Skills', and the destination 'native targets'. This distinguishes it from siblings like sync_instructions and other skill manipulation tools.

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?

No explicit guidance on when to use this tool versus alternatives. The description does not specify when to use sync_skills over sync_instructions or other skill-related tools, nor does it mention any preconditions or use cases.

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