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

With no annotations, the description carries the full burden of disclosure. It explains the sequential chaining and max operations, but omits significant side effects: the delivery parameter can write bytes to a presigned PUT URL or POST to a callback URL. The response section only mentions 'Processed image binary,' potentially misleading the agent into thinking inline delivery is always used. This is a notable transparency gap.

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 core description is concise and front-loaded with a clear purpose. However, the response section is bloated with repeated 'Content-Type' and 'Example Response' lines that are identical and add confusion rather than value. This redundancy detracts from the overall conciseness.

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?

The tool has a complex schema, no annotations, and no output schema. The description covers the pipeline concept and limit, but does not explain the delivery mode variations or how the return value differs when delivery is not inline. It also lacks error handling or authentication context. Given the complexity, this description is minimally viable but leaves important 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 description coverage is 67%, so the description should compensate. However, it adds no parameter-specific meaning beyond what the schema already provides. The 'Max 10 operations' constraint is already present in the operations parameter description. The 'image is fetched once' note is a behavioral trait, not a parameter semantic. The delivery parameter is completely absent from the description, relying entirely on the schema.

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 starts with 'Run a multi-step image pipeline' and details 'Chain multiple operations (resize, compress, convert, crop) in sequence.' This clearly identifies the tool's specific function of combining image operations, distinguishing it from single-operation siblings like resize_image and compress_image.

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 provides clear context for when to use this tool: when multiple operations need to be chained. It states the image is fetched once and each operation applies to the previous output, plus the 10-operation limit. It does not explicitly name alternatives or exclusion criteria, but the multi-step versus single-step distinction is implied by the sibling tool names.

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