aso_search_hints

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

With no annotations, the description carries the full burden and does well: it discloses no-auth/free access, that results come in Apple's own popularity order, that expand=True appends a–z to build a keyword universe, and critically that an endpoint error returns ok:False rather than an empty list. Rate limits and the effect of the country parameter are not covered, keeping it below 5.

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?

Dense and front-loaded: the core identity ('App Store autocomplete = REAL search demand') leads, followed by role, then behavior and error semantics. Every sentence adds information with no padding.

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?

An output schema exists so return values need not be explained, and the description covers the gate logic and error-handling caveat well. The remaining gap is the country parameter's impact on results, which an agent would need to know for non-US stores.

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 must compensate. It explains expand=True thoroughly (a–z expansion, keyword universe collection) and term is self-evident, but the country parameter and its effect on locale-specific results are entirely undocumented in both schema and description.

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+resource ('App Store autocomplete') and its semantic meaning ('REAL search demand'), plus its role as an 'IDEA-STAGE HARD GATE'. An agent can distinguish this from sibling ASO tools like aso_find_available_name or aso_niche_score without opening the schema.

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?

Gives a clear decision rule for when to use it (idea-stage validation) and how to interpret results (0 suggestions → REJECT the idea). It does not explicitly name competing sibling tools or exclusions, so it stops short of a 5.

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