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

Annotations already declare readOnly, idempotent and non-destructive, so safety is covered. The description adds the genuinely important behavioral fact that this does not render an image — it returns a prompt stack and an aspect_ratio to feed elsewhere — which an agent could not infer from the annotations alone. It does not detail the prompt stack's contents or size.

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?

Three tight sentences, aesthetic identity and output shape front-loaded, with the generate_image handoff last. No filler, though the em-dash clause is slightly convoluted and could be split for faster scanning.

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?

With no output schema, the description correctly takes on the job of saying what comes back and how to consume it. What is missing is minor: whether 'subject' is optional and what the prompt stack looks like when subject is omitted.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning to the style enum by spelling out the camera/lens behind each option (Canon R5 + 85mm f/1.2 vs Hasselblad H6D + 80mm). The aspect_ratio return-and-reuse note also clarifies that parameter's downstream purpose beyond the schema wording.

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 opening line names a specific aesthetic ('Golden-hour rim-light editorial portrait') and the body states exactly what the tool produces: a styled prompt stack plus an aspect_ratio. This distinguishes it in spirit from siblings like apply_high_fashion_editorial or apply_graphic_editorial_portrait, though it never names those siblings to make the boundary explicit.

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 gives clear downstream context — pair with generate_image and pass the returned aspect_ratio along — which is the main 'how to use' an agent needs. It stops short of stating when to pick this portrait style over the other portrait styles in the sibling list, so the choice between them is left to aesthetic inference.

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