get_sales_and_traffic

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only mentions 'via report' but does not state that the tool is read-only, whether it triggers report generation, or any rate limits. No information about response structure or potential side effects.

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 short sentence in Spanish, which is concise but potentially problematic for English-speaking audiences. It lacks structure (e.g., separate usage notes) and omits critical details, making it too brief for adequate understanding.

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?

Given the complexity (sales and traffic data from Amazon reports) and the presence of many sibling tools, the description is incomplete. It does not specify data granularity, refresh cadence, or how the report is generated. The output schema exists but is not referenced.

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 0%, and the description does not explain the parameters 'days_back' or 'marketplace'. It does not indicate what units days_back uses (e.g., last N days from today) or acceptable marketplace values. The description adds minimal value beyond the schema's titles.

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 states it retrieves sessions, conversion, and Buy Box percentage per ASIN via a report, matching the tool name. It is specific enough to differentiate from siblings like get_sales_summary or get_sales_rankings, though it lacks detail on the time period or report source.

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 on when to use this tool versus alternatives such as get_sales_summary or get_sales_rankings. The description does not indicate prerequisites, data freshness, or limitations.

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