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

Annotations provide readOnlyHint and idempotentHint. The description adds key behavioral context by disclosing that the tool returns a prompt stack rather than an image, and details the three style variants. No contradictions with annotations.

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 three sentences, front-loaded with the core purpose. Each sentence earns its place: aesthetic definition, flavor list, and output/workflow. No fluff or redundancy.

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 simple 2-parameter tool with no output schema, the description covers purpose, flavor options, and the essential workflow (pair with generate_image). It could be more explicit about the output stack structure, but the combination of schema and description is 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 coverage is 100% with detailed enum descriptions (e.g., 'digital_phone = Sony A7IV + 50mm f/1.4 GM phone-style realism') and subject examples. The description merely restates the three flavor names without adding new parameter meaning, so it stays at the baseline.

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 tool creates a 'phone-shot amateur look' with specific aesthetic qualities ('casual, candid, pore-level real'), and lists three distinct flavors. It also states it 'returns the styled prompt stack' for pairing with generate_image, distinguishing it from sibling apply_* tools.

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?

Provides clear context for when to use (when a realistic, candid phone aesthetic is desired) and instructs to 'pair it with generate_image.' It does not explicitly list alternatives or exclusions, but the specialized purpose makes the usage obvious.

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