synthesize_skills

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

No annotations provided, so the description carries full burden. It discloses that the tool pulls top matching skills, merges them, deduplicates, returns a provenance-tagged digest, and materializes source skills on disk. This is transparent, though it could mention how 'top matching' is determined.

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 efficient and front-loaded, starting with the core action and then providing usage context, alternatives, parameter guidance, and output summary. It is succinct but could be slightly more streamlined.

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 no output schema, the description adequately explains the return format (deduped, provenance-tagged digest plus materialized files) and input parameters. For a tool with two simple required parameters and no nested objects, this is fairly complete. It does not detail the selection criteria for 'top matching,' but that is acceptable.

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 description coverage is 100%, so baseline is 3. The description adds minor clarification by explaining how to use each parameter (e.g., 'pass your task as query and your stack + constraints as context'), which is helpful but not essential 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's purpose: pulling the best rules from top community skills and merging them into a cross-source playbook. It specifies the action (synthesize/merge), resource (skills), and scope (broad tasks), and distinguishes from sibling load_skill.

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?

Explicitly describes when to use (broad 'how should I approach X' tasks spanning multiple skills) and when not to (single skill -> use load_skill). Also clarifies required parameters and their roles.

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