search_keywords_by_app

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

Annotations already provide readOnlyHint, idempotentHint, etc. The description adds value by specifying that pagination and hosting filters are ignored, and by noting that productId is a path segment. This behavioral context goes beyond what annotations convey.

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 reasonably concise, front-loading the purpose and return format. It includes a spec link for reference but avoids redundancy. Could be slightly more structured, but overall efficient.

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 provides the return format. It covers the required parameter (productId) and filter parameters. With annotations providing safety profile, the description is fairly complete for a reporting query 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%, so baseline is 3. The description adds meaning by listing the filters (aggregation/startDate/endDate) and noting that pagination/hosting are ignored. It also includes the return structure which implies parameter impact, exceeding the baseline.

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 returns 'Top search keywords for one app' and provides the return structure. It distinguishes the tool's scope (one app) but does not explicitly differentiate from sibling tools like search_keywords_by_app_export or search_keywords_by_source.

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 on when to use this tool versus alternatives. The description mentions filters but does not explain the use case or exclude other tools. For example, it does not mention that search_keywords_by_app_export is for exporting results or that other keyword tools focus on different sources.

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