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

With no annotations, the description carries the full burden. It usefully discloses that EXIF/GPS location data is removed before storage and lists supported formats, but it omits key behavioral details such as permission requirements, whether the operation is reversible, how many photos can be added, and what happens if the request is already sent or the image exceeds limits.

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?

Two tightly written sentences with no filler. The purpose and the key behavioral note about location data removal are front-loaded and easy to parse.

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?

Output schema exists, so return values need not be explained. Still, for a mutation tool with no annotations, the description leaves gaps around authentication, error conditions, photo-count limits, and the exact consequence of trying to add a photo to a request that has already been sent.

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 0%, so the description must compensate. It clarifies that image_base64 must be base64 and lists accepted formats (JPEG, PNG, WebP, HEIC, TIFF), which adds value. However, it does not explain request_id or mention the schema's maxLength limit of about 11 MB.

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 uses a specific verb and resource: 'Add one photo' to 'a request you have not sent yet.' It also names supported image formats, making the tool's scope clear. It stops short of explicitly distinguishing this from sibling tools like homeowner_sendRequest or media_requestUpload.

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 phrase 'to a request you have not sent yet' gives an implied usage condition and implicitly rules out sent requests. However, it does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or what to do if the request is already sent.

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