Export intake data

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

Adds value beyond annotations by stating data is exported without sensitive fields, default row limit is 500, omitted rows are reported, and the CLI alternative for full exports. No contradiction with read-only/idempotent 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 concise sentences front-load the purpose and key behaviors. Every sentence adds value with no redundancy.

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?

Provides sufficient context for an agent to select and invoke the tool correctly, covering format, defaults, scoping, and fallback. Lacks explicit output structure, but the return format (JSONL/CSV) is stated.

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?

Adds practical guidance for since/until and max_rows parameters, explaining how to scope and that omitted rows are reported. The response_format parameter is not mentioned, but schema coverage is 60%, so the description compensates well.

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 it exports local intake data as JSONL/CSV without provider secrets/tokens. It specifies the default of 500 most-recent rows and mentions date scoping and max_rows, distinguishing it from similar list tools and the CLI alternative.

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 tells when to use date scoping or max_rows to refine the export, and advises using the CLI for full unbounded dumps. Provides clear context for usage and alternatives.

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