zero_search_results_keywords_export

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

Description discloses key behaviors: returns full JSON array directly (up to 500 rows), truncation on large responses, and that invalid accept format yields HTTP 400. Annotations already cover safety; description adds response format and limits.

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 plus a spec link, no wasted words. Key information (export variant, direct JSON output) is front-loaded.

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 output format, row limit, truncation behavior, and format options. Missing details on empty results and exact truncation mechanism, but adequate for an export tool.

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?

Input schema already provides 100% coverage with descriptions for all 4 parameters. Description adds no new parameter semantics beyond the schema, meeting baseline for high schema coverage.

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?

Description clearly states it exports zero-result keywords as a JSON array. It distinguishes from HAL-download exports but does not explicitly differentiate from the base zero_search_results_keywords tool (non-export).

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?

No direct guidance on when to use this tool versus alternatives like zero_search_results_keywords or other export tools. The description implies it for full data vs. download links but lacks explicit selection criteria.

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