appstore_search

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

The description adds useful behavioral context by explaining the effect of ids_only=true and the platform enum values, which go beyond the schema. However, it omits details about pagination, default language/country, and the exact return format, and with no annotations provided, the description carries the full burden.

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?

Three short sentences: the first states the core purpose, the second and third highlight key parameter behaviors. Every sentence is informative, with no repetition of schema information, making it concise and well-structured.

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 simple search tool, the description covers the essential functionality and key flags (ids_only, platform). It doesn't describe the return format or explain pagination semantics, but the schema handles parameter details, and the absence of an output schema makes some gaps acceptable.

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 describes all seven parameters with clear explanations, including the platform enum and ids_only behavior. The description adds minimal new meaning beyond confirming the same details, so it meets the baseline for high schema coverage.

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 'Search the App Store' with a specific verb and resource, and clarifies that it returns search results for a term. This distinguishes it from sibling tools like appstore_app (get app details) or appstore_reviews (get reviews), though it doesn't explicitly name alternatives.

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 a clear context for when to use this tool: when searching the App Store for apps matching a term. It doesn't explicitly mention alternatives or exclusion criteria, but the purpose is direct and unmistakable.

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