search_keywords_partner_export

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

Adds significant behavioral context beyond annotations: describes broken export links, how JSON vs CSV outputs differ, the structure of JSON response, and that invalid accept parameter returns HTTP 400. This is a high-value disclosure that prevents misuse.

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 efficient, front-loading the core purpose and including a crucial warning about broken links. It is slightly long due to the warning and spec URL, but all sentences contribute meaningful information.

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?

Given no output schema, the description thoroughly explains both output formats (JSON inline payload structure and CSV string). Covers all filters, default behaviors, and error cases. Provides a spec link for further reference. Fulfills all informational needs 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?

Schema coverage is 100% with descriptions for all parameters. The description adds context by noting that 'json' is the default accept option and that invalid values cause an error. It also clarifies the date formats are ISO and that aggregation defaults to 'week'.

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?

Clearly states it is an export variant of partner-wide search keywords. Differentiates from sibling 'search_keywords_partner' by noting the same payload for JSON and the CSV option. Also lists filters (aggregation/startDate/endDate).

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?

Provides clear context: it is for exporting data in JSON or CSV format. Warns about broken `_links.export` URLs, advising to use inline data or CSV instead. Does not explicitly state when to use this tool over alternatives, but the purpose is specific enough.

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