comfy_replay_technique

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safe-read behavior is covered. The description adds only 'including workflow', which is a slight enhancement but does not disclose behaviors like error handling, payload size, or pagination. It is consistent with annotations, so no contradiction.

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 very short (two sentences) and front-loaded with the core purpose. No filler words or redundant details, which is good. However, the Args repetition is redundant with the schema and could be removed without loss.

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?

For a simple get-by-ID tool with output schema and read-only annotations, the description is serviceable but minimal. It doesn't mention how to obtain a technique_id (e.g., via list/search), what 'full technique data' includes beyond workflow, or any potential size/performance implications. With a richer output schema, the description could be more informative but is not dangerously incomplete.

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?

The input schema has a single required parameter `technique_id` with no description. The description merely reiterates 'The technique ID to retrieve' without adding context like where to find it or what format it expects (e.g., UUID vs. name). Since schema coverage is 0%, the description fails to compensate with additional meaning.

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 action ('Get'), the resource ('full technique data'), and the intent ('for re-use'), making it distinct from listing or searching techniques. However, it does not explicitly differentiate itself from sibling tools like comfy_list_techniques or comfy_export_workflow.

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 gives a hint of purpose ('for re-use') but provides no explicit guidance on when to use this tool over alternatives like comfy_list_techniques, comfy_search_techniques, or comfy_get_workflow. There is no mention of when not to use it or which sibling tools might be more appropriate.

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