generate_hd

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

With no annotations, the description carries full burden. It discloses the cost ($0.50 USDC on Base mainnet) and that it returns a URL, but omits details like required authentication, idempotency, rate limits, or whether the URL is temporary. The cost is a notable behavioral trait.

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?

The description is two sentences with no filler. It front-loads the action and quality, then states return value and cost. Every word adds 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?

Given no output schema, the description mentions return of a URL but lacks details like expiration, file format, or resolution specifics. For a paid tool, more context on what the URL contains would be helpful. It is minimally adequate.

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 no additional meaning beyond the schema's parameter descriptions (prompt and aspect). The schema already explains prompt as text and aspect as enum with default.

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 that the tool generates a premium AI image upscaled 4x HD and returns a high-resolution image URL. The verb, resource, and quality are specific, and 'HD' differentiates it from sibling tools like 'generate_clean' or 'generate_pro'.

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?

The description implies usage for high-quality images with upscaling and mentions cost, but does not explicitly state when to use this tool versus alternatives like generate_clean or generate_image. No when-not-to-use guidance is provided.

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