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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows this is a safe, read-only operation. The description adds specific behavioral context by detailing the exact checks performed (missing URLs, weak alt text, etc.), which enhances transparency 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?

The description is a single sentence that immediately states the purpose and lists the audit criteria. It is front-loaded with all key information and contains no unnecessary words.

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 description lists the checks performed, which is adequate for a simple audit tool. However, the input schema for 'images' is underdefined (array of objects with no schema), and there is no output schema. This leaves gaps about expected input structure and return format.

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 50%: the 'platform' parameter has a brief description, but 'images' is an array of objects with no description in schema or tool description. The tool description does not clarify the expected structure of the image objects, so it adds no meaning beyond 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 clearly states the tool audits product image metadata for specific issues: missing URLs, weak alt text, low dimensions, duplicate URLs, and main-image readiness. The verb 'audit' and resource 'product image metadata' are specific, and the listed checks distinguish it from sibling tools like 'csv_cleaner' or 'duplicate_sku_finder'.

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 no guidance on when to use this tool vs alternatives. It does not mention contexts where the tool is appropriate, prerequisites, or situations where other tools would be better suited.

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