datasets_apps_search

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

With no annotations, the description must carry the burden of behavioral disclosure. It mentions 'resolved' apps and 'search index' but does not state whether the tool is read-only, describe the return format, pagination limits, or any operational constraints. This leaves significant unknowns for an agent invoking the tool.

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 concise and front-loaded: one clear purpose sentence followed by three compact enum definitions. Every sentence adds relevant information, and there is no redundant phrasing or unnecessary detail.

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?

For a 12-parameter optional search tool, the description covers the core scope and enums, which is helpful. However, it lacks any mention of return values, pagination behavior, or output structure, and since there is no output schema, these omissions leave gaps. It is minimally adequate but not comprehensive.

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 the baseline is 3. The description adds meaningful value beyond the schema by clarifying that the platform filter applies only to iOS records and by framing the store parameter as covering resolved apps from both stores. This extra context is not present in the schema descriptions.

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 explicitly states the tool searches the apps-intelligence dataset, specifying that it covers resolved iOS App Store and Google Play apps. This specific verb-resource pairing distinguishes it from live store search tools like appstore_search and googleplay_search, and provides clear scope.

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 implies use cases through the 'apps-intelligence dataset' and 'resolved apps' phrasing, suggesting this is for querying a pre-built index rather than live stores. However, it does not explicitly name alternatives or state when to prefer this tool over appstore_search, datasets_apps_charts_search, or similar siblings.

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