rhino_environment_set

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

Annotations already indicate readOnlyHint=false, so the description adds no behavioral context beyond that. It does not disclose side effects (e.g., overwriting existing environment, viewport changes) or any irreversible actions. With annotations present, the description should still add value, but it falls short.

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 a single sentence with no wasted words. It is front-loaded with the action and resource. However, it could benefit from slightly more structure (e.g., listing key parameters or usage notes).

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 the tool's complexity (single required parameter, defaults) and existence of an output schema, the description does not explain what the tool returns or any prerequisites (e.g., Rhino must be running, bridge must be active). The 'bridge only' hint is helpful but insufficient for full context.

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 input schema already provides descriptions for all parameters, so the baseline is 3. The description reinforces the purpose of use_for_lighting and use_for_background booleans but adds no new meaning beyond the schema. Schema description coverage appears high despite context signal claiming 0%.

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 action ('Attach') and the resource ('HDRI/EXR environment'), specifying its purpose for lighting and background. It also notes 'bridge only', which helps distinguish from other environment-related tools, though it could explicitly differentiate from siblings like rhino_light_add.

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 only mentions 'bridge only' as a usage constraint but provides no explicit guidance on when to use this tool versus alternatives (e.g., rhino_light_add or render settings). There is no mention of prerequisites 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.