scene_info

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

The name and 'Current...' phrasing imply a read-only snapshot, but the description never explicitly states that it does not modify the scene or what happens if no scene is loaded. With no annotations, this lack of explicit side-effect disclosure is a minor gap.

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?

One terse, front-loaded sentence that lists the important scene categories without extra prose. The parenthetical clarifies that pattern pieces include arrangement point and fabric data.

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?

Without an output schema, the description should clarify the shape or granularity of the returned data; the category list helps but leaves open whether it returns IDs, names, full objects, or counts. The presence of many sibling introspection tools also creates a need to mention what makes scene_info the right broad-scope call.

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 parametersbool Result. The description compensates well by enumerating the scene's subcomponents (project, avatars, pattern pieces, fabrics, colorways, seams), giving the agent a concrete sense of what information will be available. Baseline for zero-param tools is 4.

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 identifies the resource ('Current CLO scene') and enumerates the main content categories: project, avatars, pattern pieces, fabrics, colorways, and seams. It communicates the purpose of returning an overview of the scene, though it lacks an explicit verb like 'returns' or 'lists.'

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?

No guidance is given about when to use scene_info versus sibling tools like scene_open, pattern_list, fabric_list, seams, or avatar_list. The description does not mention prerequisites, such as needing an open scene, nor when this broad scene view should be preferred over targeted sub-resource getters.

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