export_chats

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

Annotations already declare readOnlyHint=false, openWorldHint=true and destructiveHint=false, so the write-side safety profile is covered. The description confirms the local-file write target, which is useful context, but says nothing about overwriting existing files, output size, or whether the directory must exist.

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?

A single tight sentence that front-loads the verb, scope, and destination with no filler. It is appropriately sized, though its brevity is partly what leaves usage gaps elsewhere.

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?

An output schema exists and the input schema is fully documented, so return-value explanation is unnecessary. However, for a tool that writes files into a user-supplied directory, the description should at minimum mention overwrite behavior or expected output layout; that gap keeps it at minimum-viable.

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 every parameter (since, formats, directory, conversation_match) is already documented in the schema, including the txt/md/json format values and the default set. The description adds no filtering or format semantics beyond that, so baseline 3 applies.

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 (Export) and resource (full chat history) plus the destination (local files), so the agent knows this is a file-producing operation rather than a read. It does not explicitly differentiate itself from siblings like list_conversations or get_messages, but the export-to-disk framing is distinct enough in practice.

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 no when-to-use guidance, no prerequisites, and never references the sibling tools. An agent must infer that this is the tool to pick when materializing chats on disk rather than querying them.

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