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

The description discloses that the tool performs a network download and a multipart upload/attach operation, which is consistent with the non-read-only annotation. It does not contradict annotations and adds some behavioral context beyond the raw flags.

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 primary description is concise and front-loaded, but the 'Guidance' section repeats the same sentence verbatim and adds no new information. This redundancy prevents a higher score.

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?

For a simple upload operation, the description and parameter list provide enough context to call the tool correctly. It lacks an explicit success/return description, but that is not critical given the low complexity and no output schema.

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?

All three parameters have descriptions in the schema, and the tool description does not add additional meaning beyond those. Since schema coverage is 100%, a baseline score of 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 clearly states the tool downloads a PDF from a URL and attaches it to a product via multipart upload. This distinguishes it from sibling tools like shop_upload_product_slide or shop_delete_product_pdf.

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 is provided on when to use this tool instead of alternatives, such as uploading a slide or deleting a PDF. The 'Guidance' text merely repeats the description rather than offering selection criteria.

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