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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), it discloses server-side fetching, auto-generated thumbnail/hero/full variants, content moderation, the moderation_status values, and the fact that a rejected/escalated photo blocks publishing. That is exactly the consequence-level detail an agent needs.

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 action and its single-call advantage are front-loaded, and the remaining sentences cover constraints and moderation outcomes. It is dense rather than padded, though a touch long for a two-parameter tool.

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 no output schema, the description compensates by describing the returned snapshot and moderation_status/moderation_reason fields, plus the publishing impact. Nothing an agent needs to invoke it correctly 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% and both parameters are fully documented there, so the baseline is 3. The description restates the https/routable-host constraint already in the schema rather than adding new meaning, so it does not exceed the baseline.

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?

States a specific verb (attach) and resource (photo to a listing you own) and explicitly contrasts the single-call URL ingestion with the separate 'sign/upload/confirm' flow, which lets an agent distinguish it from sign_attachment_upload and confirm_attachment_upload without opening their schemas.

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?

It clearly frames when to use this tool — direct ingestion from a public URL rather than the multi-step sign/upload/confirm path — and states acceptance conditions (https, publicly routable host). It doesn't name the sibling tools outright, so the routing is implied rather than explicit.

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