marketplace_analytics_overview

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

With no annotations provided, the description carries the full burden. It enumerates the analytics categories returned, providing some behavioral transparency, but does not explicitly state that this is a read-only operation, mention rate limits, or describe the response structure.

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, with the primary action and scope front-loaded. It uses no unnecessary words and is easy to parse.

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 read-only analytics tool with a single optional parameter, the description gives a solid overview of purpose and metrics included. It lacks explicit output format details and alternative tool guidance, but is otherwise sufficient.

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 schema provides full coverage for the single optional parameter (periodDays) with a clear description, so the baseline of 3 applies. The tool description adds no additional parameter semantics beyond what the schema already provides.

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 tool retrieves comprehensive platform-wide analytics with a specific list of metrics (volume, users, growth, revenue, funnel). The phrase 'platform-wide' distinguishes it from more targeted marketplace analytics siblings like marketplace_stats or marketplace_creator_analytics.

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 advises using this tool to understand overall marketplace health and trends, which provides clear context for when to invoke it. However, it does not explicitly name alternative tools for narrower queries, so it stops short of a 5.

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