comfy_get_categories

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, establishing it as a safe read operation. The description adds behavioral detail by specifying the output is a sorted list with node counts, which goes beyond the annotations and provides useful context about the return format.

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 minimal and front-loaded: the purpose is stated in the first sentence, and the return format is given in a concise second sentence. No superfluous information or waste; every part earns its place.

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, parameterless read-only getter with annotations covering safety, the description is complete. It specifies the return content (sorted list with counts) which complements the likely output schema. No further context is necessary for this tool's simplicity.

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?

With zero parameters, schema coverage is trivially 100%. The description adds no parameter-related meaning because there are none to explain, aligning with the baseline of 4 for 0-parameter tools. It provides sufficient clarity without needing param documentation.

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's purpose: 'Get all node categories.' It uses a specific verb and resource, and additionally specifies the return includes sorted list and node counts, which distinguishes it from siblings like comfy_list_node_types (which lists node types rather than categories).

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?

No guidance is provided on when to use this tool versus alternatives such as comfy_list_node_types or comfy_search_nodes. There is no mention of contexts, exclusions, or alternatives, leaving the agent without explicit usage direction.

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