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

Annotations declare readOnlyHint=false with destructiveHint=false/idempotentHint=false, so the description adding the 72-hour zip retention and the 10-minute link lifetime provides meaningful lifecycle context an agent would otherwise have to infer. It does not explain the async/waiting semantics ('once it's ready') in detail, but the key behavioral facts are surfaced.

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 tight sentences with no filler; the primary action is front-loaded and the branch condition follows immediately. Every clause 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?

With no output schema, the description adequately explains the return (a 10-minute download link) and the artifact's retention window. Minor gaps remain around what happens if the export is not ready and whether filtering parameters change the zip contents, but the core async contract 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?

Schema description coverage is 100%, so all three parameters are already documented in the schema. The description only elaborates on exportId's role in the two-call flow; dueForRemoval and conversationIds get no additional 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?

States a specific verb and resource ('Prepare a zip of the workspace's chat media') and covers both modes of the tool (start export vs. fetch link). An agent can tell this apart from siblings like neuron_clear_media, neuron_upload_media, or neuron_storage_job without opening the schema.

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 gives the when-to-use conditions: call without exportId to start an export, call with exportId once it's ready. This is a clear invocation flow, though it does not name alternative tools (e.g., storage_job, export_contacts) or say when not to use this tool.

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