generate_skill

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

With no annotations, the description carries the burden and does disclose meaningful behavior: template mode emits a server canonical template, optimized mode augments via Client LLM Sampling while always preserving PDCA differences, the first three tools' purposes, and session_id continuation rules. Still omits file-writing semantics such as overwrite behavior, permissions, and the default output location.

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 compact, front-loaded paragraph that opens with the deliverable and keeps each clause informative. Dense but no filler sentences.

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?

An output schema exists, so return values need not be described, and purpose/mode behavior are well covered. However, with no annotations, two undocumented parameters, and unaddressed file-write semantics, it is only minimally complete for a generation tool.

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 0%, so the description must compensate. It thoroughly explains the meaning of the mode enum values, but says nothing about output_dir or customization, leaving two of three parameters undocumented in both schema and description.

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?

States a specific verb and deliverable (產生/generate a PxDCA SKILL.md) and clarifies scope by noting it does not create a requirements session, which differentiates it from generate_requirements. It is clear what is produced, though it never names the sibling tools it competes with.

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?

Explains the two modes (template vs optimized) and what each produces, and gives an explicit exclusion ('此 Tool 不建立需求 session') that routes session-creation needs to generate_requirements. Lacks a positive 'use this when' statement against the other generate_* siblings.

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