compose_asset_preset

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

No annotations are provided, so the description carries the full burden. It indicates the output is 'compact assets and ordered layers,' but does not disclose whether the operation mutates state, has side effects, requires specific prior steps, or what happens on invalid preset IDs.

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, front-loaded sentence with no filler. Every phrase—'one scene preset,' 'compact assets,' 'ordered layers,' 'single low-token request'—adds useful information without redundancy.

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 tool with one parameter and no output schema, the description gives a reasonable summary of input and output, but it omits important context: the definition of a scene preset, whether the operation is read-only or creates/modifies state, and what an agent should do if no preset exists. Sibling context suggests more composition guidance would help.

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 schema only defines 'id' as a string with minLength 1 and has no parameter descriptions. The tool description mentions 'one scene preset,' which helps the agent infer that 'id' is a scene preset identifier, but it does not explicitly bind the parameter to that meaning or explain where the ID comes from.

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 and resource: 'compose one scene preset' into 'compact assets and ordered layers.' It clearly states the tool's main purpose so an agent can infer what it does, though it does not explicitly differentiate it from sibling tools like compose_asset_scene or compose_asset_scene_animation.

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 implies the usage context: when an agent has a single scene preset and wants a compact, low-token asset/layer result. However, it gives no explicit guidance about when to prefer this over related tools such as compose_asset_scene, generate_asset_preset, or plan_asset_scene.

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