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

Beyond the annotations, the description discloses that metadata is stripped, that images remain private until selected in an owner-published snapshot, and that confidential content should never be uploaded. This adds meaningful behavioral context without contradicting the 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 tight and front-loaded, with each sentence adding a distinct piece of information: what to upload, format/size constraints, metadata handling, privacy behavior, and a warning. There is no filler.

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?

It covers the most important input semantics and privacy expectations, but it omits what the 'application' parameter should contain and gives no indication of the response or follow-up result. Given there is no output schema, these gaps leave the agent with some uncertainty.

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 prose gives useful meaning for base64 (allowed formats, size limit) and kind (screenshot vs icon), which the schema only partially conveys. However, the required 'application' parameter is left unexplained, and the low schema coverage means the description does not fully compensate for all parameters.

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 states a specific action — uploading a real screenshot or app icon — with explicit formats and size limits. It clearly distinguishes this tool from the sibling generate_icon by emphasizing that the upload must be a real image.

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 indicates this is the path for uploading actual screenshots or icons, and it sets a firm exclusion by warning against confidential content. However, it does not explicitly name alternatives such as generate_icon or state exact conditions for choosing between them.

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