list_log_exports

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

Annotations already indicate this is read-only and idempotent, so the description's additional disclosure of the Enterprise-gating and 403 error behavior adds value. However, it doesn't mention pagination or other behavioral nuances that might matter for listing jobs, though with output schema present this is less critical.

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 concise and well-structured: the first sentence defines the action, the second provides usage context, and the third states a critical limitation. No wasted words; every sentence earns its place.

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?

For a list tool with a simple single-parameter schema and an output schema, the description covers the core purpose, usage, and error condition. The only minor gap is not explicitly mentioning pagination or ordering, but the output schema likely covers return structure. Overall complete for its complexity.

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 provides 100% coverage for the single parameter, workspace_id, with a clear description. The tool description merely reiterates 'in a workspace' without adding further meaning beyond the schema, so it meets the baseline but doesn't exceed it.

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 lists log export jobs in a workspace with status, filters, and timestamps. It distinguishes itself from related tools by explicitly positioning it as the way to find an export_id before using other log export operations.

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 gives explicit when-to-use guidance: 'Use this to find an export_id before calling get_log_export, start_log_export, cancel_log_export, or download_log_export.' It also discloses a restriction (Enterprise-gated, returns 403 on non-Enterprise plans), which helps the agent decide if this tool is appropriate in context.

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