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

With no annotations, the description carries the full behavioral burden. It discloses the diagnostic/repair output, the scope limitation, and the per-call cost/payment mechanism (USDC on Base via x402), though it does not detail authentication beyond payment or any rate limits.

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 core action, followed by precise usage and exclusion guidance, then payment context. Every sentence earns its place and there is no redundant filler.

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?

There is no output schema or annotations, so the description must cover behavior, usage, and output expectations. It states that a corrected JSON fix is returned and covers when to use it, but it does not describe the return structure or payment/authentication flow in detail.

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?

There is one parameter with 100% schema description coverage, so the schema already documents the query field. The description does not add format, syntax, or validation detail beyond the schema, making the baseline score of 3 appropriate.

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 states a specific verb and resource: diagnose a ComfyUI API-prompt execution error and return a verified fix with corrected JSON. It clearly carves out API prompts versus drag-and-drop UI workflows, but it does not explicitly distinguish itself from the sibling tool diagnose_comfyui_ops.

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?

It gives explicit when-to-use conditions: API workflow failures at queue time with missing/invalid input errors or node type mismatches. It also gives a clear when-not-to-use exclusion: drag-and-drop UI workflow issues, API prompts only.

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