operator_brands_by_competition

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

Annotations already declare readOnlyHint=true, indicating safe read-only operation. The description adds context that the tool returns brands ranked by competition level. It does not disclose potential rate limits, error handling, or authentication needs, but given the annotation, the description adds sufficient behavioral clarity.

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, well-structured sentence followed by example queries. It is front-loaded with the core purpose and avoids unnecessary words, making it easy to scan.

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 14 parameters and no output schema, the description lacks important details: no explanation of the return format (e.g., fields in results), no error handling or edge case guidance, and insufficient differentiation from sibling tools like 'brands_gaining_sellers' or 'find_undercompeted_brands'.

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 29%, meaning many parameters lack descriptions. The tool description does not explain individual parameters beyond the general purpose. It does not compensate for the low coverage, leaving many filter parameters (e.g., brand_contains, min_competitor_count) unexplained.

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 the action: given operator names, return brands ranked by competition. It includes specific example queries, which cover the tool's scope and distinguish it from other tools.

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 provides clear when-to-use examples (e.g., 'which brands sold by these operators have the least competition'). It does not explicitly state when not to use or suggest alternatives, but the examples offer strong guidance for appropriate usage.

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