environment_info

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

With no annotations provided, the description carries the full behavioral burden. It does disclose one meaningful trait: the check is non-mutating toward configuration. However, it says nothing about what is reported back (versions, paths, availability) or what happens if Blender is absent, which matters given there is no output schema.

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?

A single front-loaded sentence with no filler. The action and its non-mutating guarantee are packed into one clause pair and nothing is wasted.

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 zero-parameter probe this is close to adequate, but with no output schema the description should say what the check returns (runner/Blender versions or paths) so an agent knows what it will learn before calling. That gap keeps it at minimum-viable rather than complete.

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 the schema imposes nothing to interpret. Per the baseline for param-less tools, a 4 is appropriate; there is no parameter surface the description needs to explain.

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 states a specific verb ('Check') and resource ('installed runner and Blender'), making the tool's function immediately legible. It does not explicitly name a sibling to differentiate from, but the environment-inspection scope is distinct from pipeline_run, blender_script, and the status tools.

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?

There is no statement of when to call this versus alternatives such as diagnose_stage or pipeline_status, and no prerequisites or ordering guidance. The clause 'without changing configuration' is a safety property rather than usage guidance, so the agent is left to infer the call context.

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