listing__upload_screenshot

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

Even though annotations already mark readOnlyHint=false, the description adds valuable behavioral context: it 'handles Apple’s reserve/upload/commit sequence and the checksum,' and discloses that it's a 'PUBLIC-level write' where the image appears after Apple processes it. This goes beyond the structured 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 three sentences, each earning its place: purpose, input summary, and behavioral caveat. It is front-loaded and packs essential information without verbosity.

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 no output schema, the description explains the full work flow, including the hidden sequence, the fact that it's a public write, and that Apple processes asynchronously. This is sufficient for an agent to understand the tool's scope and effects.

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 100%, so baseline is 3. The description maps user-facing concepts (app, locale, device size, file path) to parameters but adds no new meaning beyond what the schema already provides. Version is not mentioned but is optional and already described 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?

The description opens with a specific verb and resource: 'Upload a screenshot image file to an app’s store listing in one step.' It distinguishes itself from the raw screenshot tool by explicitly noting that the raw tool 'reserves a slot and moves no bytes,' clarifying exactly what this tool does differently.

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 gives clear guidance by contrasting with the raw screenshot tool: 'the raw screenshot tool reserves a slot and moves no bytes.' This implies you should use this tool when you actually want to upload file bytes, making the when-to-use decision explicit.

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