get_store_summary

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

The description clearly discloses that the endpoint is returning a 500 Internal Server Error, which is a critical behavioral trait beyond the schema. It also explicitly identifies it as a server-side issue, setting proper expectations for the agent.

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 short and front-loaded with the purpose. The disabled warning is a bit repetitive (mentions trying again later twice) and uses heavy formatting, but it's still concise and readable.

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 the tool's current disabled state, the description is complete: it tells the agent not to use it and why. Once enabled, it lacks details on what statistics are returned, but the disabled notice is the most urgent contextual information.

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 67%, and the description adds no parameter semantics beyond what the schema already provides. Since the schema defines parameters like os, categories, and date ranges, the description doesn't compensate for missing parameter details.

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 opens with 'Get app store summary statistics,' which clearly states the tool's function. However, it doesn't specify what kind of summary statistics or how they differ from sibling tools like get_download_estimates or category_ranking_summary.

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 explicitly warns that the tool is temporarily disabled and advises contacting support or retrying later, which is important context. However, it offers no guidance on when to use this tool versus alternatives, and the disabled notice is a when-not rather than a when-to.

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