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

With no annotations, the description carries the full burden and does so thoroughly. It discloses that the tool does not upload by itself, returns a time-limited curl command, never fetches/generates/resizes/substitutes images, is idempotent for resending, never deletes, and requires an account-scoped bearer token plus confirmation. This is exceptional disclosure.

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 long but densely informative, with no filler. The critical limitation ('uploads nothing by itself') is front-loaded in an IMPORTANT block, followed by clear sections on purpose, constraints, safety, and auth. Every sentence contributes operational knowledge an agent needs.

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?

Despite lacking an output schema, the description fully explains what the tool returns (an exact curl command per file), its validity window, scoping, auth requirements, and file constraints. The agent has enough information to invoke it correctly and understand the side-effect profile without guessing.

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?

The schema already covers all parameters (100% coverage), so the baseline is 3. The description adds valuable semantics beyond the schema: the 'best first' order becomes the gallery order, paths must be verified or the command fails, files should be PNG/JPG at 1280x720, and the product is contextualized as account-scoped. These supplementary details justify a 4.

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, resource and outcome: attach real product screenshots already on disk to a tracked product. It also connects the purpose to sibling tools (check_submission_readiness and generate_submission_kit) by explaining the missing-screenshot blockage, making it clearly distinct from the broader sibling list.

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 a concrete trigger condition: use it when check_submission_readiness or generate_submission_kit report screenshots as missing, and it explains why it matters (unblocks five directories requiring a gallery). It does not explicitly state 'when not to use' alternatives, but the use case is specific and actionable.

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