get_environment

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

The description transparently states that local probes degrade gracefully when a workspace path is not configured or tools are unavailable, which is important behavioral information. Without annotations, this provides useful context beyond the basic purpose.

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 extremely concise (two sentences) and front-loaded with the main purpose. Every sentence adds value without redundancy.

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?

Given no parameters and no output schema, the description effectively covers the tool's scope (remote and local probes, graceful degradation). It could list the exact fields returned, but the context is adequate for an environment info 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?

There are no parameters, so the description needs no parameter-level detail. The baseline for zero parameters is 4, and the description suffices without adding param-specific 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 the tool reports ComfyUI environment info, mirroring `comfy-cli env`, and specifies it includes both remote system stats and local probes. This distinguishes it from siblings like `get_system_stats` by being more comprehensive.

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 implies usage for getting comprehensive environment info but does not explicitly state when to use this tool versus alternatives like `get_system_stats` or when not to use it.

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