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

Annotations already provide readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds no further behavioral details (e.g., side effects, limitations, file size caps) beyond the transformation options. The repeated 'FREE' is irrelevant and doesn't contribute behavioral transparency. With good annotation coverage, the added value is limited.

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 a compact two sentences that effectively cover the tool's capabilities. However, the 'FREE. (FREE)' is duplicative noise that doesn't add value, detracting from the overall conciseness. It earns a 3 rather than a 4.

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?

With 8 parameters and no output schema, the description covers the primary capabilities and supported options. It mentions output formats (TIFF/PDF) and paper sizes, which aligns with schema enums. It stops short of explaining the response structure (e.g., a download link or binary), but given the rich schema and annotations, the description is reasonably complete for an initial understanding.

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 coverage is 100%, and each parameter has a description. The description mentions DPI, bleed, crop marks, sizes, and output formats, but these are also in the schema. It doesn't add meaning beyond the schema, such as explaining the custom size dependency or the base64 encoding requirement. 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?

The description uses a specific verb ('Prepare') and resource ('images for professional printing') and lists concrete processing details (DPI, bleed margins, crop marks). This clearly distinguishes it from sibling tools like resize_image or convert_color_profile. It also mentions output formats and supported paper sizes, making the tool's scope unmistakable.

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 phrase 'for professional printing' clearly frames when this tool should be used. It doesn't explicitly name alternatives or when-not-to-use, but the print-specific context is enough to infer it's the right choice for print-ready output. Could be improved by explicitly contrasting with resize_image/convert_color_profile, but that's not required for a clear context.

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