update_log_export

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

Annotations provide safety profile (not read-only, not destructive, not idempotent). Description adds behavioral constraint: only certain fields are mutable after creation. No contradiction.

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 sentences, each dense with information. No wasted words. Front-loaded with purpose and timing.

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 output schema exists and annotations are present, description covers purpose, usage, constraints, and workflow. Complete for an update tool.

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 100% with descriptions. Description adds meaning by specifying which parameters are changeable after creation, providing workflow context beyond 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 verb 'Update' and the resource 'log export configuration', and specifies the timing 'before or between export runs'. It distinguishes from siblings by noting the workflow with get_log_export and start_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?

Explicitly states when to use ('before or between export runs'), what can change (only workspace_id, time_of_generation_max, requested_fields), and provides workflow: use get_log_export to review, then update, then start_log_export.

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