creative_studio_compose

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

No annotations are provided, so the description carries the burden. It reveals that the tool creates a new run directory and provenance manifest, uses headless Chromium, requires the 'creative' extra, and handles Japanese text rendering. This is meaningful side-effect and prerequisite context beyond what the schema or name provides.

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?

Three sentences, front-loaded with the primary purpose, then key technical detail and prerequisite. No filler; each sentence adds useful context.

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 description covers input (visual/copy/template/formats), output (PNGs in new run directory with manifest), tech behavior, and install requirement. It doesn't detail return values, but no output schema exists and the run-directory statement is sufficient for an agent to understand the result. Minor ambiguity about where the brand kit/logo comes from (no parameter) prevents a 5.

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 descriptions cover 100% of parameters, so the baseline is 3. The description reiterates the template/formats/copy parameters in prose and mentions the typography layer containing badge/logo, but adds little syntax or value beyond the schema. The badge's template-specific behavior is already noted in the schema.

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 a specific verb ('composite') and the resource transformation: ad copy + brand kit + key visual → per-format banner PNGs. It distinguishes itself from sibling tools like creative_studio_generate_visual and creative_studio_edit_visual by describing the composition/final render workflow.

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 tells the agent to pick a template and formats and pass copy, implying usage for rendering banner ads from an existing visual. However, it does not explicitly state when to prefer this over sibling tools or mention exclusions/alternatives, so guidance is mostly implied rather than explicit.

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