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

Goes well beyond the readOnly/idempotent annotations: it discloses that the page opens already signed in as the customer's connected browser session, that the call requires a signed-in Printdash account, and that an unauthenticated call triggers a sign-in prompt on printdash.io. It also states the state precondition under which the call fails.

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?

Front-loaded with what the tool returns, then usage, then failure conditions, then auth — a sensible order with no filler sentences. The opening sentence is a verbless fragment, which costs a little immediacy.

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 nested-target tool with an output schema and full annotation coverage, the description supplies everything an agent needs: what is returned, which page per target kind, the auth prerequisite, the refusal condition, and when to prefer it over in-chat upload. Nothing material is missing.

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%, so the baseline is 3; the description earns above that by explaining the semantic mapping behind each `kind` value (cart_line → checkout, quote_line → quote page, order_item → order page), which is more than the schema's parenthetical source hints. It adds nothing on `side` or `design`, but those are already fully documented in 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?

Names a concrete resource: the printdash.io-hosted uploader page for a specific line, and enumerates which page it is per target kind (checkout, quote page, order page). It does so with a sentence fragment rather than an explicit verb like "returns a URL", and it does not explicitly differentiate from the attach_artwork* / request_artwork_upload siblings, so it stops short of a 5.

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?

Gives an explicit triggering condition ("Use it when the customer has the file but the chat cannot send it") that directly discriminates against the attach_artwork* siblings, plus an explicit refusal condition ("Refused when the line's artwork can no longer change"). Both the when and the when-not are stated, leaving nothing to inference.

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