wb_analytics_brand_share_parents

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It only states what the tool conceptually returns and does not describe output format, date-range behavior, read-only nature, or any other operational traits beyond the minimal purpose.

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 concise sentence with no filler. It front-loads the core concept and adds context about being input for brand-share, though it is under-specified rather than richly concise.

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 four parameters, no annotations, and no output schema, the description is too thin to fully support correct invocation. It does not explain the meaning of the required date range, what the response will contain, or how the output should be fed into a brand-share call. The sibling context provides some orientation but does not fill these gaps.

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 25%, with just 'locale' briefly documented. The description adds slight clarity by indicating that 'brand' refers to the brand whose parent categories are returned, but it leaves date_from and date_to completely unexplained, and the locale values are only partially covered by the schema.

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 identifies a specific resource ('parent categories of a brand') and frames it as input for brand-share, which helps distinguish it from wb_analytics_brand_share and wb_analytics_brand_share_brands. However, it lacks an explicit verb such as 'get' or 'list', so it reads more like a noun phrase than a clear operation.

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 phrase 'input for brand-share' implies this tool should be used as a preparatory lookup before running brand-share analytics, and the sibling name wb_analytics_brand_share_parents reinforces that. There is no explicit statement of when to use it versus wb_analytics_brand_share_brands or wb_analytics_brand_share, nor any when-not-to-use guidance.

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