bridge_generate_theme

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the output contents (surfaces, text, palette, shadows, spacing) and that contrast is validated internally. However, it says nothing about determinism, output format/side effects, or whether it writes files or returns a spec, which an agent would want to know.

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?

A single front-loaded sentence listing the generated artifacts with zero preamble or filler. It is dense but every clause (surfaces/text, palette, shadows, spacing, contrast) maps to real output, so nothing is wasted.

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 4-parameter tool with a nested preferences object, the description adequately conveys what is produced and the schema fully documents inputs, and no output schema means return values need not be explained. The remaining gaps are behavioral (output format, side effects) and routing against the ten sibling generators, which leave the definition only minimally complete.

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 color, colors, preferences, and the color_scheme enum in detail. The description adds only the framing that the system is 'built on a brand color,' which is already in the schema. Baseline 3 is correct 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?

States a specific verb (Generate) and resource (a complete dark mode theme), enumerating the concrete artifacts produced: dark surfaces and text, adjusted palette, shadows, spacing, with contrast checked. This makes it distinguishable from narrower siblings like harmony_generate_palette or chord_generate_shadows, though it never explicitly names or routes against them.

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?

There is no when-to-use guidance, no exclusions, and no mention of the alternatives among the many generation siblings (harmony_generate_palette, chord_generate_shadows, pitch_audit_contrast, etc.). 'Contrast checked' weakly implies pitch_audit_contrast may be redundant, but this is left entirely to inference.

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