find_brands_with_high_seller_churn

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

Annotations already declare readOnlyHint=true. The description adds context about the filtering logic (delta vs category, default threshold) which is helpful but not extensive. No contradictions.

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?

Three sentences, front-loaded with purpose, no redundant information. Every sentence 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?

Core purpose and metric are clear, but the tool has 13 parameters and no output schema. The description does not explain the shape of the results or how the multiple optional filters interact, leaving some ambiguity for complete usage.

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 62%, between the 50-80% range. The description only explains two parameters (min_delta_pp and category) implicitly, leaving many others (e.g., scope, marketplace, brand filters) unexplained. It does not adequately compensate for undocumented parameters.

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 finds brands with high seller churn relative to category, specifying the metric and threshold. It uses a specific verb ('find') and resource ('brands'), but does not explicitly distinguish from siblings like 'brands_gaining_sellers'.

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?

Description provides explicit usage hints ('Use when the user asks about...') that guide typical queries. However, it does not mention when not to use the tool or suggest alternatives from the sibling list.

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