Get Redshift Capabilities

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

With no annotations, the description carries the full burden. It explicitly discloses the key behavioral trait of non-mutation ('without mutating the scene'), which is valuable. However, it does not mention any other behavioral aspects like whether the tool requires a scene, whether it can fail, or what form the report takes.

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, focused sentence that front-loads the core action ('Report exact') and packs all relevant details into a compact list. No filler or repetition.

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 no-parameter, read-only capability-reporting tool, the description clarifies what areas are covered and promises non-mutation. It doesn't describe the output structure, but with no output schema this is a minor gap; the tool appears complete enough for an agent to select and invoke 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 tool has zero parameters and the schema is empty, so there is nothing for the description to add. The baseline of 4 for zero-parameter tools applies, and the description does not need to compensate for any parameter documentation gaps.

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 ('Report') and a specific resource ('Redshift ... capabilities'), enumerating exact areas of support (renderer, module, node-space, AOV, light, camera, render). It clearly distinguishes itself from the generic sibling 'get_capabilities' by scoping to Redshift and from 'rs_list_aovs' by describing support rather than listing AOVs.

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 phrase 'without mutating the scene' implies this is a safe introspection call, but there is no explicit guidance about when to use it over other tools such as 'get_capabilities' or 'rs_list_aovs'. Usage context is only implied, not stated with alternatives or exclusions.

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