generate_role_skill

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

The description discloses side effects ('Writes SKILL.md + assets/playbook.yml to disk'), scope ('no scripts/'), and return behavior ('Returns the SKILL.md content as str, or {"error": str} on failure'). This adds meaningful context beyond the idempotentHint annotation, though it does not explicitly mention overwriting behavior or permissions.

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?

Two sentences with no filler. The first sentence states the core action; the second provides essential behavioral details (file writes and return type). Every clause earns its place.

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?

With full parameter schema coverage, an output schema, and an idempotency annotation, the description suffices for a focused tool. It explains what is generated, where it is written, and what is returned. The only notable gap is explicit usage guidance versus siblings, but overall the context is adequate.

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 the schema already details both role_name and install_to. The description adds little parameter-specific meaning beyond 'for one role,' but the schema carries the full burden, making a baseline 3 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 a specific verb and resource: 'Generate a skill package for one role.' It further specifies outputs (SKILL.md + assets/playbook.yml) and distinguishes itself from sibling tools by focusing on a single role rather than plugins, collections, or generic skills.

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 like generate_plugin_skill or generate_collection_skills. The phrase 'for one role' implies a role-specific use case, but there are no stated exclusions, prerequisites, or comparisons to siblings.

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