resize_for_platform

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

No annotations provided, so the description must disclose behavior fully. It states AI generative fill usage but omits key details: whether the tool actually resizes or only returns a URL, the output format, error handling, or permissions. The implication of mutation (resizing) is ambiguous.

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?

Two sentences are concise and efficient. The purpose is front-loaded, but the second sentence could be integrated more tightly. No unnecessary information.

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?

No output schema and no annotations, so description must compensate. It fails to explain the tool's output (e.g., URL object vs string), how to use the result, or any constraints. Edge cases (e.g., what if aspect ratio is similar?) are unaddressed.

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 descriptions cover all parameters (100% coverage). The description adds context for useGenFill (auto-detect based on aspect ratio difference), but does not enhance semantics for other parameters. Baseline 3 is appropriate.

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?

Description clearly states the tool generates a Cloudinary transformation URL for resizing for a specific platform. It distinguishes from general resize tools by specifying 'advertising platform/channel', but does not explicitly contrast with siblings like batch_resize or generate_transform_url.

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?

No guidance on when to use this tool vs alternatives. The description implies platform-specific use but does not mention exclusions, prerequisites, or appropriate contexts. Siblings exist but are not referenced.

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