googleplay_search

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

The description only states it returns results for a term. It does not disclose behavioral traits such as pagination, sorting, rate limits, authentication needs, or the scope of search (e.g., apps only vs. other content). Since no annotations are provided, the description carries full burden but is minimal.

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 extremely concise with two sentences. It front-loads the core action ('Search Google Play') and immediately states the output. No unnecessary words.

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 search tool with 6 parameters but no output schema, the description is somewhat lacking. It does not explain the format or content of results, nor does it clarify parameter interactions (e.g., how 'full_detail' and 'num' affect output). It is adequate for a simple search but not fully complete.

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?

The input schema already provides descriptions for all 6 parameters (100% coverage). The description adds no extra meaning beyond the schema, such as usage examples or relationships between parameters. Baseline 3 is appropriate.

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 verb 'Search' and the resource 'Google Play', and indicates it returns results for a term. This distinguishes it from sibling tools like googleplay_app (specific app details) and googleplay_similar (similar apps).

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 provides no guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or context for choosing this tool over other Google Play tools (e.g., googleplay_list, googleplay_suggest).

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