googleplay_app

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

No annotations provided, so the description carries full responsibility. It mentions defaults for country and lang but omits behavioral traits such as rate limits, error handling, or authentication requirements. Limited disclosure of side effects or underlying behavior.

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 two sentences: first sets purpose, second lists contents and defaults. No unnecessary words, front-loaded, and optimally concise.

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?

The description lists key return fields (installs, ratings, etc.) and defaults, which is informative given no output schema. Could mention potential errors or pagination, but covers the essential structure adequately.

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% with descriptions for each parameter. The description adds value by providing default values for country ('us') and lang ('en'), which clarifies optional parameter behavior beyond the schema.

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 'Retrieve full Google Play app details' and enumerates specific metadata fields (installs, ratings, pricing, etc.), distinguishing it from sibling tools like googleplay_search (search) or googleplay_reviews (only reviews).

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 does not explicitly guide when to use this tool vs alternatives. It lists the tool's scope but lacks direct comparisons or when-not-to-use advice. Usage context is implied by the mention of 'full app details' and siblings' names.

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