dump_threads

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

The annotation already declares readOnlyHint=true, so the description only needs to add extra behavioral nuance. It does mention thread persistence and cold-reload, which is useful context beyond the annotation, but it does not clarify whether the export writes files to disk (only the schema does for markdown) or describe any side effects. No contradiction with annotations.

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, with the primary purpose front-loaded. The second sentence is a bit of a run-on ('Use thread_ids to filter specific threads, format to choose output') but is still concise and informative. No wasted words.

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 simple two-parameter tool with no required fields and no output schema, the description plus schema covers the main usage: exporting threads with optional filtering and format selection. The persistence/cold-reload note adds valuable context. Could mention the default behavior (all threads) but that is already in the schema.

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%, with both parameters (format and thread_ids) already documented in detail. The description merely echoes 'Use thread_ids to filter specific threads, format to choose output' without adding new semantic information. Baseline 3 applies since schema carries the load.

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 starts with a specific verb and resource: 'Export conversation threads as JSON or Markdown.' It clearly identifies the tool's function and distinguishes it from sibling tools like chat and listmodels, which involve interaction and model listing respectively.

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 provides implicit usage context: 'Threads persist to disk and can be cold-reloaded after memory expiry' suggests using this tool for backup or recovery after memory loss. It does not explicitly name alternatives or exclusions, but the context is clear enough for an agent to infer when this tool is appropriate.

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