search_keywords_by_app_export

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

Discloses that the return payload is identical to `search_keywords_by_app`, that the export links are broken, and that data comes inline. Annotations already indicate read-only, idempotent, non-destructive; description adds critical behavioral caveats without contradiction.

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?

Packs essential information (purpose, behavior, broken feature, spec link) into two sentences plus a note. Front-loaded with verb+resource, uses symbols for emphasis, no wasted words.

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 specifies the return structure (`_links`, `summary`, `details`) and addresses the broken export URLs. Includes a reference to the API spec. Covers all relevant aspects 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 has 100% coverage with descriptions. The description adds that `productId` is a path segment, but provides no further semantic enrichment for other parameters. Schema already handles parameter meaning adequately.

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 'Export variant of per-app search keywords' and explicitly contrasts with 'search_keywords_by_app', distinguishing it from the sibling tool. Specific verb 'export' and resource 'per-app search keywords' with inline return data description.

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 warns about broken `_links.export` URLs and advises using inline data directly. It implies usage for export scenarios but does not explicitly compare to other export siblings like `search_keywords_by_source_export`. The warning provides important usage context.

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