generate_node_skill

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

With no annotations, the description fully discloses all behaviors: read-through caching, network operations (fetching README, scanning Python code, using GITHUB_TOKEN), optional server enrichment, and file writing side effects. No contradictions.

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 front-loaded with the main purpose and progressively adds details. Every sentence is informative, though slightly longer than necessary. It is well-structured and concise.

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 complexity (3 params, no output schema), the description covers functionality, side effects, and dependencies well. The return format is mentioned but not fully detailed; still sufficient for an AI agent.

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%, so baseline is 3. The description adds valuable context beyond schema: cache behavior for refresh, recursive directory creation for install_in, and dual nature of source. This enriches agent understanding.

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 generates a SKILL.md documenting a ComfyUI custom node pack, specifying the source as registry ID or GitHub URL. This is a specific verb+resource that distinguishes it from siblings like scaffold_custom_node or get_node_pack_details.

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 explains when to use the tool (to document a custom node pack) and details options like cache bypass and install_in. It mentions prerequisites (internet access, optional GITHUB_TOKEN) but does not explicitly state when not to use it or suggest alternatives, though the tool's uniqueness mitigates this.

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