Generate an image

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

Annotations are absent, so the description carries the transparency burden. It discloses cost behavior ('Runs on your SayMaker credits', 'reports the exact credit cost') and clarifies pricing invariance ('vague prompts cost the same as precise ones'). It doesn't address async/failure behavior, but the wait parameter's schema description covers task-id polling.

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?

Two sentences with no filler. The core purpose and return value are front-loaded, followed by actionable cost and prompt-quality guidance. Every clause 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?

For a five-parameter tool with no output schema or annotations, the description covers purpose, return value, cost, and prompt-quality guidance. Parameter specifics are already in the schema. A minor gap is that the unconditional 'return its URL' does not mention the wait=false task-id path, though the wait parameter's schema description fills that in.

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 baseline is 3. The description adds prompt-construction semantics beyond the schema by recommending that users name subject, framing, light, and material, and by noting that vague prompts have equal cost. This genuinely helps agents produce better prompts.

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 names a specific verb ('Generate'), resource ('an image from a text prompt'), platform ('saymaker.ai'), and result ('return its URL'). This clearly distinguishes it from siblings like edit_image and generate_video, whose purposes are different operations.

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?

It implies when to use it: whenever a new text-prompt image is needed. It offers no explicit when-not-to-use guidance or alternatives, such as using edit_image for existing images or generate_video for motion, so the selection context is 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.