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

Annotations already declare readOnlyHint=false and destructiveHint=false, so the description's mutation profile is consistent with the schema. The description adds value by disclosing the output artifact ('producing a PNG with transparency'), signaling a non-destructive transform that returns a new file rather than modifying the input in place. No contradiction 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 a compact two-clause sentence that front-loads the verb and resource and emits the key output trait in the second clause. Minor redundancy: the leading 'Add Drop Shadow' repeats the title before adding anything new, which slightly dilutes the otherwise tight structure.

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 covers the essential return trait ('PNG with transparency'), and all 7 parameters are documented in the schema. The only gap is the vague optional output_format parameter, whose allowed values and interaction with the always-PNG claim are not specified.

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%, and the schema descriptions go well beyond typical naming: blur explains the 0 = hard-edged case, opacity scopes its effect to the shadow layer only, file lists accepted formats and the 25 MB cap plus the BMP exclusion, and shadow_color explicitly warns about the field name. The main description adds no parameter detail, but the schema fully compensates, so the agent is exceptionally well informed about how to invoke each parameter.

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 names a specific verb ('Add') and resource ('drop shadow effect to an image'), plus a distinctive output trait ('producing a PNG with transparency'). Within the sibling list of photo_* tools (photo_watermark, photo_image_overlay, photo_editor), none targets drop shadows, so the purpose is unambiguous without opening the schema.

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 niche effect ('drop shadow') plus the output constraint ('PNG with transparency') give a clear context for when to select this tool. The file parameter adds an explicit exclusion — 'BMP is NOT accepted here, unlike most photo tools' — though the main description stops short of naming alternative tools or explicitly routing between them.

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