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

The description discloses important methodology: it uses brand-level first-seen rather than per-ASIN counts and is stable under scraper-coverage growth. This adds meaningful context beyond the readOnlyHint and destructiveHint annotations, though it does not describe the output shape or edge-case behavior.

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 dense but every sentence earns its place: definition, methodology caveat, and usage signals. The key concept is front-loaded, and the user-trigger list is compactly placed at the end.

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?

This is a detection tool with no output schema, yet the description does not explain what the return value looks like (e.g., boolean, threat level, or signal details). It covers the why-and-when well, but an agent may not know how to interpret the tool's result.

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 coverage is 100%, so the schema already documents all five parameters, including defaults and allowed values. The description adds no extra parameter-specific semantics beyond the algorithmic context, so the baseline score of 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 what the tool does: 'Detect whether a brand is under competitive attack' and precisely defines the detection via elevated new-entrant rate combined with buy-box churn. It also distinguishes its methodology from the inflated per-ASIN count, which separates it from related seller-count 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 explicit when-to-use guidance with concrete user phrasings like 'is my brand being targeted' and 'new sellers flooding my listings.' It does not, however, mention alternatives or when not to use this tool, so it stops short of a full 5.

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