set_config

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states that the tool sets global rendering parameters, without mentioning side effects, persistence, or whether it requires specific state (e.g., before rendering). The added 'IMPORTANT' note does not disclose any behavior of this tool.

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 first sentence is concise and front-loaded. The second sentence, 'IMPORTANT: Always use MCP tools for scene operations,' is unrelated to the tool's specific function and adds noise rather than value, making the description less efficient than it could be.

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?

Although the schema documents the parameter and an output schema exists, the description lacks essential usage context: when to apply global rendering configuration, how it relates to other set_* tools, and any behavioral implications. The tool is simple, but the description leaves the agent without guidance on when to invoke it.

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?

Schema description coverage is 100%, with the 'config' parameter already listing supported keys (background_color, resolution, fps, frame_height). The description adds no parameter-specific meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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's function with a specific verb and resource: 'Set global rendering configuration parameters.' It is distinguishable from sibling tools like set_camera and set_color by the word 'global,' but it does not explicitly differentiate from those alternatives.

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 provides no guidance on when to use this tool versus alternatives. The 'IMPORTANT' note about using MCP tools for scene operations is a general system instruction and does not clarify usage context or exclusions for set_config.

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