img_optimize_delivery

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It says 'Generate optimized image delivery setup' but does not reveal whether the tool writes files, modifies configuration, requires an API key, or has any side effects in the project directory. The Pro feature note adds no behavioral detail.

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 compact and front-loaded, placing the action and resource in the first few words. It contains no filler, though it is concise at the expense of necessary detail.

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 that there are no annotations and no output schema, the description is too sparse for an agent to understand what 'delivery setup' actually produces, what inputs matter, or what a successful invocation looks like. The required 'directory' parameter is mentioned in the schema but not in the description, leaving the tool's overall context incomplete.

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?

With schema description coverage at 50%, only 'directory' is documented, and the description adds no explanation of either parameter. 'api_key' is entirely unexplained, and the description does not clarify whether it is a Pro entitlement key or an optional credential. The low coverage is not compensated by the description.

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 states a specific verb and resource: 'Generate optimized image delivery setup.' It conveys that the tool creates a configuration for delivering optimized images, which is distinct from the sibling image tools focused on processors or resizing. However, 'setup' is left somewhat broad, so it falls short of a 5.

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?

There is no guidance on when to use this tool versus the many sibling image-related tools, such as img_generate_processor or img_add_resize. The only extra signal is '(Pro feature)', which hints at licensing but not usage context. An agent must infer the appropriate invocation time.

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