google-play-search

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

With no annotations provided, the description must disclose behavioral traits, but it only states the purpose without mentioning any side effects, permissions, rate limits, or result formats. No information about search behavior (e.g., pagination, exact vs. fuzzy matching) is given.

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 at one sentence, but it is under-specified. It does not provide enough information to justify its brevity, as critical details are missing.

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?

Given the tool has 5 parameters, many siblings, and an output schema that is not referenced, the description is severely incomplete. It fails to cover basic usage context, parameter constraints, or expected output.

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%, and the description adds no information about parameters. The schema provides names and defaults but no explanation of valid values (e.g., 'price' default 'all' but no enumeration of allowed values).

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 'Search for apps in Google Play Store' clearly states the verb 'search' and resource 'apps', but it is generic and does not differentiate from sibling tools like 'google-play-list' or 'google-play-app', which may also involve searching or retrieving 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?

No guidance is provided on when to use this tool versus alternatives such as 'google-play-list' or 'google-play-suggest'. There are no exclusion criteria or context for optimal usage.

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