start_log_export

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

The description discloses that the tool is asynchronous, only queues the export, and does not return rows/download file. This goes beyond the annotations (which already indicate non-read-only, non-destructive, non-idempotent, open-world). It adds valuable 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 three sentences, each adding value: purpose, async behavior and what it does not do, and lifecycle direction. It is concise and well-structured.

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 the tool has one parameter, full schema coverage, and an output schema (existing but not shown), the description covers the asynchronous behavior and the full lifecycle (create, start, poll, download). It is complete.

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 has one parameter 'export_id' with a clear description. Schema coverage is 100%, so the description adds no extra meaning beyond the schema. Baseline 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 'Start processing a previously created log export job,' specifying the action (start) and resource (log export job). It distinguishes from sibling tools like create_log_export and download_log_export by noting the asynchronous nature and directing to get_log_export and download_log_export.

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 it (to start a previously created export) and what not to expect (no rows/download file). It provides alternatives: use get_log_export to poll and download_log_export after completion, guiding the agent effectively.

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