get_generation_recommendations

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

With no annotations, the description carries the burden and does disclose a real operational prerequisite: 'Requires COMFYUI_HOST for resource stats,' which tells the agent the resource half of the response may be unavailable without configuration. It also surfaces domain behavior the agent cannot infer from the schema — that SD 1.5/SD XL render text poorly while FLUX and SD 3 do better, which explains why the tool returns model advice at all. Missing are any notes on failure modes beyond the host caveat or on latency of resource probing.

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?

Three sentences, front-loaded with the deliverable, then the domain rationale, then the call condition. The middle sentence about base models rendering text poorly is slightly longer than needed but earns its place by justifying the tool's existence rather than being 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?

No output schema exists, and the description compensates by naming the response contents (max resolution, model size, batch, model/setting advice). The only gap is that the specific shape of the resource stats or the form of the advice is not characterized, but for a read-only advisory tool with a fully documented single parameter this is close to sufficient.

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 description coverage is 100% with one optional parameter, so the baseline is 3. The description adds genuine meaning by stating the parameter should be the user's own image description and by explaining the conditional downstream effect (text/letter hints trigger model and setting advice), which goes beyond the schema's restatement.

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 opens with a specific verb and resource ('Get recommendations for image generation') and immediately enumerates the two payloads: system resource guidance (max resolution, model size, batch) and text-in-image advice. It is clearly distinguishable from siblings such as get_system_resources or suggest_nodes because it fuses resource planning with prompt-conditional model advice.

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 an explicit trigger ('Call when planning a txt2img or img2img workflow') and an explicit conditional ('pass the user's image description as prompt to get text-in-image advice when relevant'). No exclusion against the nearest siblings (get_system_resources, suggest_template_for_checkpoint) is given, so it falls short of the 5 bar.

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