Export Leads

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

No annotations are provided, so the description must convey side effects. It states the tool writes a file to disk, but does not disclose overwrite behavior, required permissions, return value, or whether filtering affects only the output or also the stored data. This is a write operation that lacks transparency about its consequences.

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 a single sentence of 12 words, front-loaded with the verb and resource. No extraneous info, and the key details (export, stored leads, optional filter, CSV/JSON, on disk) are all present.

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?

The tool has 12 parameters, no annotations, and an output schema (not described). The description does not cover the filtering semantics, output behavior, or file handling. A minimal viable description would at least mention that the output schema provides a file path or result, and that filter parameters narrow the exported set.

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?

With 0% schema description coverage, the description was expected to compensate. It mentions optional filtering and the two output formats, but does not explain the 12 parameters (e.g., keyword, hasEmail, minConfidence) or how they interact. The phrase 'optionally filtered' provides only a hint.

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 uses a specific verb ('Export') and resource ('stored leads'), states the output format ('CSV or JSON') and destination ('on disk'). This clearly distinguishes the tool from siblings like list_stored_leads or filter_leads, which do not persist to disk.

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 implies when to use (when needing to export leads to a file), but does not explicitly mention alternatives or exclusions. There is no comparison with list_stored_leads or filter_leads, nor guidance on when not to use.

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