skylight_import_events_from_photo

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

Beyond the destructiveHint annotation, the description reveals that the tool uploads to S3, uses an AI event_importer, returns a dry-run preview without confirm, and that the photo↔intent link is inferred from captured traffic. This adds significant behavioral context.

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 a single, well-structured paragraph that starts with the primary purpose, explains the dry-run vs upload behavior, and ends with the follow-up workflow. Every sentence adds essential information without redundancy.

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 tool's behavior, required confirmation, and post-processing steps. It mentions the dry-run preview content and the need to poll and approve. However, it doesn't detail error conditions or the exact outcome of approval, leaving minor gaps.

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 schema covers 75% of parameters with descriptions. The tool description adds value by explaining the confirm parameter's role in triggering the upload vs preview, and clarifies that image_path is an absolute path. However, it doesn't elaborate on frameId or category_ids beyond what's 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 clearly states the tool imports calendar events from a photo using Skylight's AI. It distinguishes from siblings by specifying the unique functionality of importing via photo, which no other sibling tool does.

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 explicitly says when to use confirm:true vs false, and provides a detailed post-processing workflow involving polling and approval tools. It also warns about the best-effort nature and inferred server-side link.

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