get_product_performance

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

The description declares it a read operation ('[Ads / read]') and states it is a stub in this environment, aligning with typical read-only behavior. However, with no annotations provided, the description fails to disclose other behavioral traits such as authentication requirements, rate limits, or whether it supports pagination. It is minimally transparent but not comprehensive.

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 extremely concise, consisting of one sentence that is front-loaded with the purpose. It uses keywords like '[Ads / read]' for quick scanning. However, the phrasing 'introspection stub' may be unclear to some users, and the brevity sacrifices some explanatory depth, warranting a score slightly below perfect.

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 tool has seven parameters, no output schema, and no annotations, the description is insufficiently complete. It does not explain the return value structure, pagination behavior, or provide any usage examples. An agent would lack critical context to invoke the tool correctly and interpret results.

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 has 100% parameter descriptions, so the schema itself adequately documents all seven optional parameters. The description adds no additional semantic information about the parameters, resulting in no extra value beyond the schema. Baseline 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 it retrieves 'Sponsored Products advertised-ASIN performance' with a read hint, distinguishing it from sibling tools like get_adgroup_performance or get_campaign_performance. However, it lacks explicit sibling differentiation and could be more precise about what performance metrics are included.

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?

The description implies usage for reading ad performance data but provides no guidance on when to use this tool versus alternatives like get_keyword_performance. It notes the tool is a hosted endpoint and a local stub, which is helpful for understanding its availability, but doesn't offer explicit when-to-use or when-not-to-use advice.

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