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

Annotations are present (destructiveHint=true, readOnlyHint=false, non-idempotent, open world), so the safety profile is roughly covered, but the description adds nothing beyond purpose. It omits that this is a live-payable request, that app_ids is required with a max of 20 IDs, and the US/English-only restriction noted in the schema.

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?

A single clean sentence with no filler, front-loaded on the outcome. It is efficient, though it is under-specified rather than over-long.

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?

Return values are covered by the output schema, but for a live POST endpoint whose single body parameter carries many nested fields, the description is too thin: no usage context, no constraints, and no differentiation from the many sibling labs endpoints.

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?

With only one top-level parameter (body) and reported schema description coverage of 0%, the description should carry the load, yet it mentions only the app_ids object and ignores filters, order_by, limit/offset, and the location/language constraints that live inside the nested body 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?

States a specific verb and resource: returns keywords for which the specified apps rank in the same App Store SERP. It is clear what the tool produces, but it never distinguishes itself from sibling labs tools like post_dataforseo_labs_apple_keywords_for_app_live or post_dataforseo_labs_apple_app_competitors_live.

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 intersection endpoint versus keywords_for_app, competitors, or bulk_app_metrics. The description gives a purpose but no context, prerequisites, or exclusions.

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