skylight_upload_photo

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

Beyond the destructiveHint annotation, the description discloses the two-step S3 signing and registration workflow, and explicitly states that without confirm:true no S3/network call is made. This is valuable behavioral context that helps an agent avoid unintended 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?

Three sentences, each carrying distinct information: what the tool does, how it works, and the confirm gating behavior. The most important operational detail is front-loaded.

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?

Given no output schema, the description is close to complete: it covers inputs, the confirm flag, the dry-run preview output, and side-effect behavior. Missing explicit return value details for confirm:true uploads and failure modes, but the essential call semantics are present.

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 coverage is 80%, and the description adds important semantics: image_path must be an absolute resolved path, mime type is detected, and confirm gates the network call. It clarifies the dry-run output structure, though frameId/frame_ids semantics remain mostly schema-only.

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 verb and resource: upload a photo or video from a local file to the Skylight frame slideshow. It clearly distinguishes the tool from album/message-related siblings by naming the target as the frame slideshow.

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 clearly explains when the tool performs a real upload versus a dry run, and that confirm:true is required for the actual network operation. It does not explicitly name sibling alternatives or conditions for choosing them, but the dry-run/confirm contrast provides strong usage guidance.

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