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

The annotation readOnlyHint=true already indicates a read-only operation. The description adds value by specifying the output format ('styled prompt stack') and intended usage ('pair it with generate_image'), which clarifies behavior beyond the annotation. There is no contradiction with the idempotent hint; the tool simply returns a string.

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 concise and front-loaded, with three short phrases conveying the style, variants, and output. Every sentence earns its place, and there is no wasted wording. It is well-structured for quick 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?

Given the simplicity of the tool (2 params, no output schema), the description is largely complete: it states the purpose, output, and usage guidance. The schema covers parameters, and annotations cover safety. It could benefit from explicit guidance on when not to use it or how it compares to similar apply_* tools, but it is sufficient for this level of complexity.

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 documents both parameters and their enums with examples. The tool description adds minimal extra meaning—just restating 'classic studio or golden-hour outdoor', which aligns with the schema's enum descriptions. Since the schema does the heavy lifting, a baseline score of 3 is appropriate.

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 it returns a styled prompt stack for a graphic editorial portrait, with specific style variants (classic studio or golden-hour outdoor). It uses a specific verb ('returns') and resource ('styled prompt stack'). However, it does not explicitly differentiate from sibling tools like apply_high_fashion_editorial, which could overlap in purpose.

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 ('pair it with generate_image') and mentions the two style options, giving some context for when to use it. However, it does not explicitly state when to use this tool over alternatives, nor does it provide exclusions or prerequisites. The guidance is inferred from the style description rather than explicitly stated.

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