find_deconcentrating_brands

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

Discloses that the tool compares first and second halves of a window (via 'since_weeks'), indicating temporal analysis. The readOnlyHint annotation is already present, and the description adds context about the business implication (opportunity for new entrants). 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?

Two sentences cover purpose and usage triggers. No redundant words. Each part is essential: first defines the action, second provides invocation cues.

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?

Covers overall purpose and when to use, but given 16 parameters and no output schema, more detail on default behavior, parameter interactions, and expected output would improve invocation accuracy. Adequate for a read tool but could be richer.

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?

Only 4 of 16 parameters are described in the schema (25% coverage). The tool description does not add any parameter explanations beyond what's in the schema. Key parameters like min_old_seller_count, min_control_score, etc., lack documentation, making it hard for agents to set them correctly.

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?

Uses specific verb 'find' and clear resource 'brands where buybox concentration dropped'. Includes concrete example queries covering synonyms like 'brands losing control', making purpose unmistakable. Differentiates from siblings by focusing on concentration drop rather than seller count growth.

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?

Explicitly lists user query patterns that should trigger this tool ('brands losing control', 'deconcentrating brands', etc.). No explicit exclusions or alternatives, but the examples effectively guide when to use.

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