generate_cover_imageGenerate AI cover images and upload them to Misar.Blog CDN for blog posts. Provide a prompt and optional dimensions to receive a ready-to-use image URL.
Generate a cover image using AI and upload it to the Misar.Blog CDN
| Name | Required | Description | Default |
|---|---|---|---|
| size | No | Image dimensions (default: landscape 1792x1024) | 1792x1024 |
| prompt | Yes | Description of the image to generate |
Changes observed during successful MCP inspections.
v5.1.3Input schema / properties / prompt / descriptionPrevious value: -"What the image should show, in plain language, up to 1000 characters. Describe subject and style; avoid asking for text in the image."New value: +"Description of the image to generate"Input schema / properties / size / descriptionPrevious value: -"Output dimensions: '1792x1024' landscape (the default, best for article covers), '1024x1024' square, '1024x1792' portrait."New value: +"Image dimensions (default: landscape 1792x1024)"v5.1.0Input schema / properties / prompt / descriptionPrevious value: -"Description of the image to generate"New value: +"What the image should show, in plain language, up to 1000 characters. Describe subject and style; avoid asking for text in the image."Input schema / properties / size / descriptionPrevious value: -"Image dimensions (default: landscape 1792x1024)"New value: +"Output dimensions: '1792x1024' landscape (the default, best for article covers), '1024x1024' square, '1024x1792' portrait."v2.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare this is a non-read-only, open-world, non-idempotent write, so the safety profile is covered. The description usefully adds that the image is AI-generated and pushed to a CDN, but omits cost/latency implications of the AI call and what happens if it is re-invoked for the same prompt.
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 tight sentence that front-loads the core action and appends the side effect. There is no filler, and every clause carries 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?
For a two-parameter generation tool with no output schema, the definition is adequate but thin: it implies a CDN URL results from the upload but never states the return value, generation latency, or failure modes. An agent can call it, but cannot reason about the result.
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 both 'prompt' and 'size', including the enum dimensions and default. The description adds no additional parameter semantics beyond what the schema provides, making the baseline 3 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?
States a specific verb+resource (generate a cover image) and the follow-on action (upload to the Misar.Blog CDN), which is more than a restatement of the name. However, it never contrasts itself with the sibling 'upload_image', so an agent must infer which one to reach for when a file already exists.
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?
No when-to-use or when-not-to-use guidance is given. The obvious alternative, 'upload_image', is a sibling but is never mentioned, leaving the agent to guess whether this tool ingests an existing asset or synthesizes a new one.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.