Find competitors

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

readOnlyHint=true already covers the safety profile. The description adds two behavioral traits beyond annotations: results are scoped to brands currently advertising, and they are sorted by ad volume. It says nothing about result count, pagination, or what fields come back, so the added value is modest.

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?

A single tight sentence with no wasted words, front-loading the resource ('brands in your space') before the ranking behavior. Nothing could be cut without losing meaning.

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 no parameters, no output schema, and a readOnly annotation, the main remaining question is what the agent receives. The description characterizes the return set (competitor brands ranked by ad count) adequately, though it omits result volume/limits and any notion of how 'your space' is determined.

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 tool takes zero parameters, so there is nothing for the description to disambiguate. Per the rubric, a parameterless tool sits at the baseline of 4.

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?

States a specific verb and resource ('find the brands... that are advertising') plus the ranking criterion (by ad volume), which is far more than a restatement of the name. It implicitly separates itself from search_brands (broad brand search), but never names a sibling explicitly, so sibling differentiation is left to inference.

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 'in your space that are advertising right now' implies the discovery/competitive-research use case, but there is no explicit when-to-use, no when-not-to-use, and no pointer to alternatives such as search_brands or compare_brands. Usage must be inferred.

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