create_skill_draft

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

Discloses that the draft is not published and does not write to native runtime, which is useful. But lacks details on permissions, side effects, idempotency, or what happens if a draft with the same name exists.

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?

A single, front-loaded sentence efficiently conveys the core purpose and key distinction. It could be slightly more structured but remains concise and informative.

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 existence of an output schema (not shown), return value details are not needed. However, the description omits prerequisites, error states, and when to use alternatives like 'generate_skill'. Adequate but not thorough.

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 adds no parameter information. Users must infer meanings from parameter names alone, which is insufficient for a tool with six parameters.

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 creates an 'editable draft skill' and distinguishes it by noting 'without canonical publish or native runtime writes.' This contrasts with sibling tools like 'create_skill' which likely creates a canonical version.

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?

Implies usage for creating a draft instead of a canonical skill, providing clear context. However, it does not explicitly state when not to use this tool or name alternative tools.

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