asset_generate_og_image

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

Adds substantial behavioral context beyond annotations: deterministic typography, no diffusion, server-side without API key, unsupported inline_svg mode. Informs agent about tool limitations and rendering behavior.

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 purpose, no redundant information. Each sentence earns its place.

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?

Despite good purpose and transparency, the description omits details for most parameters (6 of 8 undocumented), and no output schema or return value description. Given 8 parameters and nested objects, the description is incomplete for full parameter understanding.

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?

Adds meaning for mode and with_background_image (inline_svg unsupported, external_prompt_only conditional). However, 0% schema coverage means other parameters (title, subtitle, template, brand_bundle, background_brief, output_dir) are left undescribed. Partial compensation but not comprehensive.

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 output ('Render a 1200×630 OG image'), method ('via Satori template'), and key characteristics ('deterministic typography, no diffusion'). Distinguishes from diffusion-based generation tools among siblings.

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?

Provides guidance on mode usage: api is default and server-side, inline_svg is not supported, external_prompt_only is conditional on with_background_image. Lacks explicit comparison to sibling asset generation tools but is clear enough for its specific purpose.

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