setup_hdri_environment

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states 'Configure HDRI world shader', omitting any details about whether it creates a new shader, modifies an existing one, requires a world shader to be present, or has any side effects. This is insufficient for transparency.

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 extremely concise (one sentence), but it sacrifices meaningful content. It does not earn its place as it fails to provide essential details. A description should be appropriately sized to cover key aspects; this is under-specification, not conciseness.

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 moderate complexity (configuring an HDRI world shader), the description is severely incomplete. It does not mention the output schema (which exists but is not described), nor does it provide any context about the parameter or behavior. The agent has insufficient information to use the tool correctly.

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 has a single parameter 'kwargs' with no type, constraints, or description, and schema description coverage is 0%. The description does not explain what 'kwargs' accepts (e.g., keys like 'strength', 'rotation'), adding no value beyond the schema. The agent cannot infer correct usage.

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 'Configure HDRI world shader' clearly states the verb and resource. It is specific to HDRI world shader configuration, distinguishing it from sibling tools like 'setup_lookdev_stage' or 'apply_material_preset'. However, it lacks additional context that would make the purpose fully unambiguous.

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, such as 'setup_lookdev_stage' or 'assign_material'. There is no mention of prerequisites, use cases, or exclusion criteria, leaving the agent with no context for decision-making.

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