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

Description adds behavioral context (server-side rendering, AI limit, title default) beyond annotations but does not clarify if setting a cover overwrites the previous one, which could be seen as destructive.

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?

Information is front-loaded with the main action, followed by key details in two sentences. No unnecessary words; every sentence provides value.

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?

Covers main functionality, constraints (AI limit, host requirement), and default behavior. Missing output description (e.g., whether it returns the image URL) but overall sufficient for a mutation tool.

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?

Description provides context for prompt (vibe, palette, imagery, energy) and implies the include_title parameter, but does not explicitly describe each parameter. Schema has 0% coverage, so description adds some value but is incomplete.

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?

Description clearly states it generates a brand-new cover image from a text prompt, distinguishing itself from sibling tools like set_event_image and refine_event_cover.

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 states requirements (event_id, host role) and mentions AI-image limit constraint. Implies use case for creating a new cover without file upload, though does not explicitly list alternatives.

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