zendesk_ai_export_fetch_conversations

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

With no annotations provided, the description carries full burden. It discloses that it downloads and parses data, returns an array, and lists record fields. It also mentions the TTL constraint. No side effects are indicated, which is acceptable for a read-like operation.

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: first states the main action, second describes return type, third details record contents. No fluff, every sentence earns its place. Well 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 adequately explains the return format. It covers input provenance and constraints. Could mention error handling or pagination, but for a simple single-param tool, it is sufficiently 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?

Schema coverage is 100%, so baseline is 3. The parameter description in the schema already covers origin and TTL; the description restates this without adding new semantic details. No additional meaning 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 tool downloads and parses conversation data from a signed URL, mentioning specific output fields (conversation ID, timestamps, etc.). It distinguishes itself from siblings by explicitly referencing the complementary tool zendesk_ai_export_get_signed_urls.

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 indicates this tool must be used after obtaining a signed URL from zendesk_ai_export_get_signed_urls and within its TTL window. Although no explicit when-not-to-use or alternatives are given, the context is clear and the constraint is stated.

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