producer_generate_theme

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It does disclose a key behavioral trait: the output is WCAG AA-compliant and includes 10-step tonal palettes, which implies the tool performs color computation and contrast checking. However, it doesn't disclose whether the tool validates inputs, what happens on failure, whether it mutates any state, or whether it is idempotent. For a generation tool, this is adequate but not rich.

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, well-structured sentence that front-loads the core purpose (generates an accessible theme) and includes the key differentiator (WCAG AA, 10-step palettes). Every word earns its place, and there is no redundancy or 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?

For a generation tool with 4 parameters and no output schema, the description is reasonably complete: it states the output type and key quality attributes. However, it doesn't mention what the generated theme contains beyond palettes (e.g., typography, spacing, component tokens), nor does it explain the relationship between the seeds and the output. An agent might not know what to expect in the return value, but the core calling context is covered.

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 all four parameters. The description adds the context that the primarySeed is a brand hex color and that the output is a 10-step palette, which helps understand how the seed is used. However, it doesn't add details about the scheme parameter's effect or the neutralSeed's role beyond what the schema says. Baseline 3 is appropriate.

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 states the tool's function: generating an accessible, WCAG AA-compliant design system theme with 10-step tonal palettes. It specifies the verb (generates), the resource (design system theme), and a key differentiator (accessibility compliance, 10-step palettes). It doesn't explicitly distinguish it from siblings, but the resource and output are distinct enough from component generation, mutation, auditing, export, primitives, and Figma sync.

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 tool is for creating themes, but it doesn't explicitly state when to use it versus alternatives like producer_generate_component or producer_get_primitive. There is no mention of when not to use it or what prerequisites exist (e.g., needing a seed color). The context is clear enough for a straightforward generation task, but no explicit routing guidance is provided.

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