node_pack_git

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

With no annotations provided, the description carries full burden and excels: it discloses read-only vs write behavior, the environment flag toggle, the structured refusal mechanism, local-only constraint (COMFYUI_PATH), and path jailing. This is comprehensive transparency.

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 with no filler. It front-loads the core purpose, then efficiently layers permissions, usage context, and constraints. 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 tool's complexity (5 parameters, no output schema), the description is complete: it covers all actions, permissions, environment flag, path handling, default behavior, and workflow positioning. No significant gaps remain.

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%, yet the description adds significant meaning: it explains that commit requires a message, paths are pack-relative and jail-checked with default to all changes, and max_chars defaults to 12000. This goes well beyond the schema's basic descriptions.

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 runs git operations (status/diff/log/commit/push) inside a custom-node pack. It specifies the verb 'run' and resource 'git operation inside one custom-node pack', distinct from sibling tools that handle other steps like scaffolding or writing files.

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 explicitly states that read operations are always allowed and writes require the COMFYUI_MCP_ALLOW_GIT_WRITES flag, with a structured refusal if disabled. It also positions the tool as the final step of the author loop, giving clear context. However, it does not explicitly list when not to use it or alternative tools.

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