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

Annotations indicate a write operation (readOnlyHint=false). The description confirms import but adds no details about side effects, conflict handling, or response format. Minimal added value beyond 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?

Description is front-loaded with purpose and usage rules. Each sentence serves a purpose, though somewhat verbose. Could be tightened but not excessively long.

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 tool with 5 undocumented parameters, no output schema, and no behavioral details, the description lacks parameter explanations and return value info. It covers usage guidelines well but leaves major gaps.

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 has 5 required parameters with 0% description coverage. The description does not explain any parameter beyond the generic purpose. The agent cannot determine the role of creativeDirectionPrompt, entityObjectId, etc. from the description alone.

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 imports an image URL as a product creative asset, distinguishing it from sibling tools like edit_creative_asset and regenerate_creative_asset.

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 explicit pre-requisite checks: check business permissions, call check_business_tool_access, handle grace-period warnings, and never proceed when blocked. Includes specific constraints for FREE businesses.

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