ae_add_drop_shadow

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

With no annotations, the description carries full burden but only says 'add a soft Drop Shadow,' which implies a non-destructive addition. It does not specify side effects, prerequisites (e.g., layer must exist), or behavior when repeated. This is adequate but not thorough.

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 single, front-loaded sentence that efficiently conveys the core purpose. Every word earns its place, making it highly concise.

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 7 parameters, no output schema, and no annotations, the description lacks completeness. It does not explain required parameters (layer is required but unmentioned), the role of 'comp', or the color format, leaving gaps for correct invocation.

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 57%, meaning some parameters (comp, layer, color) lack descriptions, and the description adds no further parameter guidance. The agent must infer meanings from limited info, reducing usefulness.

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 adds a soft Drop Shadow to a layer with sensible defaults. It uses a specific verb-add and resource-drop shadow, and implicitly distinguishes from sibling tools like ae_add_effect by labeling it a convenience.

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 suggests using this for initial setup with defaults and fine-tuning via ae_set_effect_param afterward, providing good usage context. However, it does not explicitly state when to avoid this tool or compare to alternatives like ae_add_effect.

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