generate_article_hero_image

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

No annotations provided. Description says 'AI-generated visual' but omits behavioral details like async operation, credit cost, or whether it is read-only. With no annotations, the description should disclose more about the generation process and any side effects.

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 well-structured sentences that front-load the purpose and use cases. No extraneous information.

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?

No output schema is provided, and the description does not mention the result format (e.g., URL, base64, job ID). Given sibling tools like get_job_status and wait_for_job, the tool likely returns an async job reference, but this is not indicated. The description should explain the output to help an agent use the result correctly.

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 baseline is 3. Description adds context about brand style hints and reference images, but does not elaborate beyond the schema definitions.

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?

Clearly states it generates a hero banner image for blog posts, articles, etc. Lists specific use cases (CMS banners, newsletter headers, thumbnails) and differentiates from siblings like generate_social_teaser_image and generate_email_header_image.

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?

Explicitly tells when to use it for featured images and cover illustrations. Does not explicitly mention when not to use or alternatives, but the context from sibling tools provides implicit guidance.

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