rhino_environment_set

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

Annotations only provide readOnlyHint=false, so the description carries the burden of clarifying behavioral scope. It adds useful context by indicating this is a mutating 'attach' operation and that it affects both lighting and background. It does not disclose side effects like replacing an existing environment or requiring a valid absolute file path.

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 conveys the verb, resource, purpose, and scope with no filler. The parenthetical 'bridge only' is compact yet informative, and every part of the sentence earns its place.

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 relatively simple setter, the description combined with the richly detailed nested schema and output schema gives an agent enough to invoke the tool correctly. The main gaps are behavioral side effects and explicit alternative routing, but the schema covers parameter meanings and defaults well.

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?

Although the context signal reports 0% schema description coverage, the nested input schema actually documents every parameter with descriptions and defaults. The description adds some semantic value by linking HDRI/EXR files to hdri_path and clarifying the lighting/background purpose, but it does not explain rotation_deg, background_strength, or doc_id beyond what the schema already provides.

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 uses a specific verb ('Attach'), names the resource precisely ('HDRI/EXR environment'), and states its purpose ('lighting + background') plus a scope restriction ('bridge only'). It is unambiguous, though it does not explicitly name a sibling tool to differentiate from.

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 when to use the tool: when an HDRI/EXR environment needs to be attached for lighting and background in the bridge context. However, it does not explicitly mention alternatives or state when not to use this tool, leaving some selection burden on the agent.

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