Export Full Dataset

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

With no annotations, the description must carry the full behavioral burden. It discloses that the tool uses pagination to bypass the API limit, which is a valuable behavioral trait beyond what the schema shows. However, it does not mention whether this is a read-only operation (implied by 'export'), any rate limits, or potential side effects, leaving some ambiguity.

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 concise sentence that front-loads the core purpose and the key differentiator (bypassing the limit). It contains no fluff and every word earns its place.

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?

Though an output schema exists, the description is sparse for a complex export tool. It does not explain when to use it over alternatives, any operational constraints (e.g., performance implications of fetching 100,000 rows), or how the 'max_rows' parameter interacts with the pagination behavior. An agent would benefit from more context to use it correctly.

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 67%, meaning two parameters (start_date and end_date) lack descriptions in the schema. The description adds no parameter-specific information and does not compensate for the gaps, leaving the agent to infer date format constraints. The description provides zero value beyond the schema.

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 the tool exports all rows and bypasses the 5,000-row API limit via pagination. This distinguishes it from sibling tools like get_search_analytics that likely have row limits, and the verb+resource is specific and unambiguous.

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 guidance is provided on when to use this tool versus alternatives. The description does not mention circumstances that would favor export_full_dataset over get_search_analytics or other data retrieval tools, nor does it state any prerequisites or exclusions.

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