analytics_top_products

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

No annotations are provided, so the description must disclose behavioral traits. It mentions output includes revenue and percentage of total, but does not state that this is a read-only operation, how the ranking is computed, any default behavior (e.g., sort by revenue), or limitations. Lacks safety and operational context.

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, front-loaded sentence with no filler. It immediately states the action and output. Appropriate for the tool's simplicity.

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 4 parameters, no output schema, and no annotations, the description is too brief. It doesn't explain the response structure, default behavior, or usage context. While the schema documents parameters, the lack of output schema means the agent is left guessing at the return format.

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 provides 100% description coverage for all 4 parameters, so the baseline is 3. The description adds minimal semantic value beyond the schema; it only hints at the overall output, not the specific meaning of parameters like limit or sort_by, which are already documented.

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 'Obtiene' (gets) and identifies the resource as 'ranking de productos más vendidos' (ranking of best-selling products) with revenue and percentage of total. This clearly distinguishes it from sibling analytics tools like analytics_revenue or analytics_dashboard, which focus on different metrics.

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 doesn't mention scenarios, prerequisites (e.g., provider requirement), or contrast with sibling analytics tools. The description simply states what it does, leaving the agent to infer usage.

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