submit_checkout_photos

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

The description discloses that photos are 'queued for downstream inspection workflows (Phase 2 vision comparison)' and that they are logged to a maintenance/cleaning record. This adds meaningful behavioral context beyond the annotations, which are all false and therefore not very informative. The description does not contradict the annotations and provides a reasonable sense of side effects.

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 two sentences, front-loaded with the primary action and outcome. It contains no filler or redundant information, making it concise and easy to scan.

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?

The description covers the purpose, the context (post-checkout), and the downstream behavior (queued for inspection). However, there is no output schema, and the description does not explain what the tool returns (e.g., confirmation, error behavior). For a simple upload tool, this is a minor but noticeable gap.

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 input schema already provides descriptions for all three required parameters (photos, listingId, reservationId) with 100% coverage. The description adds contextual information about the purpose (post-checkout, queuing) but does not add additional parameter-specific semantics beyond what the schema already states. Baseline of 3 is appropriate.

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 clearly states the tool's function: 'Accept post-checkout photo uploads and log them to the property's maintenance/cleaning record.' This uses a specific verb ('Accept') and resource ('post-checkout photos'), and it distinguishes the tool from siblings like get_photos and update_photos by focusing on the checkout workflow and the logging/queuing aspect.

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 context is clear: this is for post-checkout photo uploads. However, it does not explicitly name alternative tools or state when not to use it. Sibling tools like get_photos and update_photos exist, but the description does not reference them or provide exclusions. This is a minor gap.

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