Render skin

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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the bar is lower; the description nonetheless adds that the operation is deterministic and never modifies files, which is a stronger guarantee than the hints alone. The output enumeration adds context even though the output schema carries the detail.

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 core purpose is front-loaded in the first clause, and the remaining sentences carry real content. The parenthetical enumerations are dense and slightly run-on, but no sentence is pure filler.

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?

With annotations covering the safety profile and an output schema covering return values, the description supplies the missing glue: what is compiled, what the review contains, and what optional outputs exist. It stops short of stating prerequisites or relationships to the sibling validation/patch tools.

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 coverage is 100%, so file/spec/focus/include are already documented in the schema; the description's "on request" phrasing loosely tracks the include flag but adds no format or syntax detail beyond what the schema provides. Baseline 3 applies when the schema does the heavy lifting.

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 and resource ("Compile a skin spec and review it") and enumerates exactly what the tool produces, which cleanly separates it from siblings like texel_validate, texel_patch, or texel_save. An agent can tell what this tool does without opening the schema.

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?

Usage is implied (render/review a skin spec) and the optional-output switch is signalled with "on request," but no when-to-use versus when-not guidance is given, and no alternative such as texel_validate or texel_render_family is named. Nothing misleading, just no explicit routing.

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