portrait_image

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

No annotations are provided, so the description carries full burden. While 'Generate' implies creation, it lacks critical behavioral details: it doesn't mention whether this is a read-only or destructive operation, what permissions are needed, rate limits, or what happens on failure. The description adds minimal behavioral context beyond the basic action.

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 extremely concise with just two clauses, front-loading the core purpose and following with the sibling relationship. Every word earns its place with zero wasted text, making it highly efficient for agent comprehension.

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 annotations and no output schema, the description is incomplete for a generative AI tool. It doesn't explain what the tool returns (e.g., image file, URL, metadata), error conditions, or behavioral constraints. While concise, it leaves significant gaps in understanding the tool's full operation and results.

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 fully documents all 6 parameters. The description adds no parameter-specific information beyond implying portrait dimensions (1024x1536), which isn't directly tied to any parameter in the schema. Baseline 3 is appropriate when the schema does all the parameter documentation work.

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 the specific action ('Generate'), resource ('portrait AI image'), and dimensions ('1024x1536'), distinguishing it from sibling tools like landscape_image and square_image by specifying portrait orientation. It also explicitly identifies it as a shortcut for generate_ai_image, providing clear differentiation.

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 explicitly states when to use this tool ('shortcut for generate_ai_image'), implying it should be used specifically for portrait images rather than the more general generate_ai_image or other sibling tools like landscape_image. This provides clear alternative guidance.

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