comfy_list_techniques

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safe-read nature is pre-known. The description adds 'newest first' (ordering behavior) and 'structured TechniqueList' (return shape), which are useful behavioral details beyond annotations. It does not cover failure modes, but for a list operation this is acceptable.

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?

Two short sentences plus a one-line args block. No filler. The description is front-loaded with the primary action and includes the parameter explanation in a structured format.

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 read-only listing tool with a simple optional parameter and an output schema, the description provides purpose, ordering, parameter, and return type information. No further context is necessary, and sibling comparisons are not required given the unambiguous action.

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 contains only 'limit' with no description, but the description's Args section fully explains it: 'Maximum number of techniques to return (default 50)'. This compensates for the 0% schema coverage and gives the agent the exact parameter semantics.

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 'List all saved workflow techniques (newest first)' with a specific verb 'List' and resource 'workflow techniques', and adds ordering detail that distinguishes it from broader listing tools. It does not explicitly compare to comfy_search_techniques, but the 'all' scope implies exhaustive listing, making ambiguity low.

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 does not provide explicit when-to-use guidance or exclusions. Sibling tools like comfy_search_techniques imply different use cases, but the description relies on common sense. It is otherwise clear for its simple purpose.

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