marketplace_get_conversion_statistics

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds only that results include both application and category-average series; it says nothing about how date ranges or granularity roll up, data freshness, rate limits, or result size, which are the behaviors an agent would need here.

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?

A single efficient sentence with no filler and the resource front-loaded. It is concise but arguably too terse given the parameter complexity it leaves unexplained.

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?

With six required parameters, a non-obvious conversion enum, low schema coverage, and no output schema, the definition is materially incomplete. An agent cannot tell what a returned 'series' contains, how the funnel conversions are keyed, or how date_from/date_to and granularity interact.

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 only 17% (just partner_id), yet the description never explains any of the six required parameters. The 'conversion' enum values (open_pending, pending_active, etc.) and the granularity/date-range semantics are left entirely undocumented, so it fails to compensate for the coverage gap.

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 uses a specific verb ('Get') and a well-defined resource ('Marketplace funnel conversion series'), and clarifies that the series covers both application-level and category-average data. It does not distinguish itself from the close sibling marketplace_get_statistics, so it falls short of a 5.

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?

There is no guidance on when to use this tool rather than marketplace_get_statistics or the other statistics/list siblings, and no prerequisites (scope, permissions, or data availability) are mentioned. Usage must be inferred entirely from the name.

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