category_new_entrants

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

Annotations already declare readOnlyHint=true. The description adds valuable behavioral context: it's an observation signal, not a confirmed first-ever entry, due to sparse re-sampling. No contradictions with annotations.

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 cover purpose, clarification, and usage examples. Front-loaded with the key action and limitation. No wasted words.

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?

The tool has 17 parameters but no output schema. The description explains the core concept and limitation, but does not describe the return format or how to interpret results. Given the complexity, more guidance on output would be beneficial.

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 only 35% (6 of 17 parameters have descriptions). The description does not provide additional meaning for the undocumented parameters (e.g., brand_contains, min_seller_count). It hints at date-related parameters but does not compensate for the low coverage.

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 it finds brands newly observed in a category within a date window, with specific verb and resource. It distinguishes from siblings by explaining it's an observation signal and provides example user queries that clarify usage.

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 includes explicit example queries (e.g., 'new brands in Electronics') and a warning about the limitation of sparse sampling. It does not explicitly list when not to use or name alternatives, but the examples sufficiently guide typical usage.

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