marketplace_search_analytics

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

With no annotations, the description must disclose behavioral traits itself. It only notes that the tool is for admin use, implying an access restriction, but says nothing about data returned, read-only nature, rate limits, or pagination. This is a significant gap for an analytics tool.

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 a single focused sentence with no fluff. It gets straight to the point and earns its place by stating the core purpose.

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 tool has no output schema and sparse annotations, so the description should explain what insights are returned and how the parameters modify results. It does neither. It also fails to disambiguate from many sibling marketplace analytics tools, making it incomplete for an agent to select correctly.

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 100% for both parameters (type and period) with descriptive enums and defaults. The tool description adds no additional meaning about how these parameters affect results, so the baseline of 3 is appropriate.

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 search analytics and insights for the marketplace, specifying an admin context. However, it does not differentiate this tool from numerous sibling analytics tools (e.g., marketplace_analytics_overview, marketplace_stats, 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?

No guidance is provided on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or other marketplace analytics tools. The only hint is the admin qualifier, which is not elaborated.

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