self_update

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

Thoroughly discloses behavioral details: auto-check on start, install mode detection, dev install never updated, npx behavior, inability to hot-swap, requirement to reconnect. No annotations present, so description carries full burden and excels.

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?

Front-loaded with main purpose, includes necessary behavioral details. Slightly verbose but each sentence adds value. Could be tightened minimally.

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?

Completeness is high given single parameter and no output schema. Covers return behavior implicitly and error cases. Sufficient for agent to use tool correctly.

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% with enum descriptions. Description adds valuable context beyond schema, e.g., 'update' action refuses on dev link and is no-op when up to date. Enhances understanding of parameter behavior.

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?

Clearly states the tool checks or applies a self-update of the comfyui-mcp npm package. Distinguishes from sibling update tools by focusing on the MCP server itself, with specific verbs and resource.

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?

Provides explicit context on when to use (check/apply self-update) and install mode detection. Implicitly excludes non-MCP updates via sibling tools. Lacks direct comparison with siblings but sufficiently guides usage.

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