art.style.compile

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

With no annotations, the description carries the full burden, and it does disclose the core transformation: merging style, optional material, and resolution into a flat object. However, it does not state whether this is purely read-only, what happens on unknown material or style definitions, or whether it depends on existing project state.

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 one dense sentence with no filler and front-loads the tool's purpose. Every phrase contributes either to what is compiled or how it is compiled.

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?

The tool has four optional parameters and no output schema or annotations, and the description introduces 'subject' and 'style definition' without connecting them to any input parameter or context dependency. An agent cannot fully determine how the style definition is selected or what the flat StyleConstraints object contains beyond its name.

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%, so the schema already documents width, height, profile, and material. The description adds that material and resolution participate in the merge, but it does not explicitly map 'resolution' to width/height or clarify how 'profile' relates to 'material'.

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 states a specific verb ('Compile'), a resource ('style constraints'), and the transformation it performs: merging style definition, optional material profile, and resolution into a flat StyleConstraints object. It is clearly distinct from retrieval or validation tools like art.get_style and art.validate_style, though it does not explicitly name an alternative sibling.

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 gives no guidance on when to use this tool versus similar style-related tools such as art.style.check, art.style.repair, or art.validate_style. There are no stated exclusions, prerequisites, or alternative conditions for an agent to route on.

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