get_tacos

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

Description uses 'Read' implying read-only, but lacks critical behavioural details: no mention of return format, pagination, rate limits, or authentication requirements. The grouping dimensions mentioned (ASIN, brand, campaign) are not present in the input schema, creating ambiguity.

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?

Single, well-structured sentence front-loads the key information. No extraneous words; every part adds value.

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?

Without an output schema, the description should explain the return value structure. It mentions TACOS blended by dimensions but does not clarify how to request specific groupings (ASIN, brand, campaign) since those are not parameters. Incomplete for an agent to invoke 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?

Input schema covers both parameters with descriptions (100% coverage), so the description adds no new information about parameters. The mention of grouping dimensions in the description is not reflected in the schema, which may confuse agents.

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?

Description clearly states the tool reads TACOS (total advertising cost of sales) with specific grouping dimensions (ASIN, brand, campaign), distinguishing it from sibling tools like get_campaign_performance or get_keyword_performance.

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?

Implied usage for retrieving TACOS data but no explicit guidance on when to use versus alternatives or exclusions. The description does not state prerequisites or when not to use this tool.

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