get_system_resources

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

With no annotations, the description carries the full burden and does so reasonably: it discloses the COMFYUI_HOST prerequisite, describes the returned fields (flux_ready, platform_hints), and explains the OOM-avoidance motive for calling early. It stops short of describing failure behavior when the host is unreachable or unreachable/invalid.

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 core purpose and the imperative usage rule before the platform caveats. The Apple Silicon parenthetical is dense but earns its place by preventing a wrong-model choice.

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 key return fields and their meaning (flux_ready threshold ~12GB VRAM, platform_hints). For a simple no-arg probe tool this is close to complete, with only error/edge behavior left unspecified.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline for a no-param tool applies. The description correctly implies a parameterless call by framing it as a station-level query.

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?

States a specific verb and resource ('Get ComfyUI station resources (GPU/VRAM/RAM)') plus the derived recommendations, which is concrete and readable without the schema. It is not, however, explicitly differentiated from the sibling get_generation_recommendations, which also returns sizing 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?

Gives an explicit ordering instruction — 'Call this first before building or executing workflows to avoid OOM' — which is exactly the kind of routing guidance an agent needs. It does not name alternatives or state when the call can be skipped.

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