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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description goes further by disclosing that the call consumes the research quota and that appStoreId yields a ranking where null means the app was absent from results. That null semantics and cost disclosure are real value beyond structured fields; only return shape granularity is left thin.

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?

Two tight sentences that lead with purpose and return content, then add the conditional appStoreId behavior and cost. Nothing is redundant or padded.

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?

With no output schema and only read-only annotations, the description supplies the essential return-value and cost information an agent needs to call it correctly. The remaining gap is per-parameter semantics for store/platform/limit, which is a schema-side deficiency rather than a description failure.

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 0%, so the description carries the burden, and it does explain the least obvious parameter (appStoreId, including null result meaning). However 'term', 'limit', 'store', and 'platform' get no described semantics — no indication that 'store' is a storefront code or that 'platform' scopes which App Store surface is searched.

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 ('Live App Store search for a keyword') plus what comes back (ranked apps, difficulty, optional app ranking). It is clearly distinguishable from sibling utilities like get_most_searched_keywords or get_keyword_popularity, though it never names a sibling explicitly to reinforce the boundary.

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?

Usage is implied rather than stated: 'Live' hints at fresh rather than historical data, and the appStoreId note implies a rank-checking use case. No explicit when-to-use/when-not-to-use guidance or alternative routing is given, so the agent must infer intent from the sibling list.

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