comfy_get_gpu_info

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint (false). Description adds no behavioral nuance beyond listing returned data (torch version, device names). It doesn't mention potential latency or prerequisites.

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?

One sentence, front-loaded with the main purpose, and lists expected information. No fluff.

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?

With annotations (readOnly, idempotent) and no parameters, the description captures the essential info. Mentions specific fields, making it complete for a simple read tool.

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?

No parameters exist, so description has nothing to add beyond schema. Baseline 4 applies because the tool is parameterless and the description correctly focuses on returns.

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?

Clear verb+resource: 'Get detailed GPU info' with explicit data points (VRAM, torch version, device names). Distinguishes from siblings like comfy_get_system_stats (system-wide stats) and comfy_free_vram (mutational).

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?

Implied usage—natural for when you need GPU-specific information. No explicit comparison to alternatives like comfy_get_system_stats or comfy_check_vram, but the scope is self-evident. No when-not conditions.

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