generate_role_skill

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

The description discloses that it writes SKILL.md and assets/playbook.yml to disk, mentions it does not write scripts/, and specifies the return format (string or error dict). This adds useful context beyond the idempotentHint annotation, though it does not cover all edge cases (e.g., file overwriting behavior).

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 concise, using three sentences with no unnecessary words. The main action is front-loaded, and every sentence adds value.

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 output schema exists (not shown but indicated), the description adequately covers the tool's side effects and return format. It lacks mention of the install_to parameter in the description, but the schema covers it, so it 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 coverage is 100%, and the description does not add additional meaning beyond what the schema already provides for the two parameters. The baseline score 3 is appropriate.

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 'Generate a skill package for one role', specifying the verb and resource. It distinguishes from sibling tools like generate_collection_skills and generate_plugin_skill by focusing on a single role, but does not explicitly contrast with them.

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 no guidance on when to use this tool versus similar siblings (e.g., generate_skill, generate_collection_skills). It does not specify prerequisites, alternatives, or conditions.

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