renderer_settings

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world behavior, so '[INSPECT] Read-only' is essentially a restatement. What the description does add is the enumeration of the configuration fields exposed, but it says nothing about return shape or freshness beyond that.

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?

Two compact fragments, with the mode tag front-loaded and the covered fields immediately after. No filler sentences.

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 no parameters, no output schema, and annotations covering the safety profile, the description's field enumeration carries most of the needed information. The only real gap is that an agent cannot tell from the description alone why it would call this instead of renderer_info.

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 there is nothing to document; the baseline of 4 applies. The field list in the description compensates by describing what the (empty) call yields.

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 resource (renderer configuration) and enumerates the concrete properties covered (toneMapping, exposure, colorSpace, shadowMap, pixelRatio), so an agent knows exactly what it returns. However, it does not differentiate itself from the sibling renderer_info, which appears to cover overlapping ground, leaving ambiguity about which to pick.

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 '[INSPECT] Read-only' tag implies this is for inspection rather than mutation, which implicitly separates it from set_renderer, but the description never states when to use this over renderer_info or names any alternative. Usage is only weakly implied.

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