List DataDive Niches

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

Annotations already declare readOnlyHint=true, and the description adds substantial behavioral context beyond that: the API does not apply paging, every page repeats the same rows, accounts with many niches return large responses, and there is no server-side search or sorting. This is exactly the kind of behavioral disclosure an agent needs.

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?

Although long, every sentence earns its place: purpose, return shape, and a critical limitation with concrete handling instructions. The TEMPORARY LIMITATION section is clearly signaled and front-loaded with actionable guidance.

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 output schema, the description still enumerates all returned fields and pagination metadata, defines what a Niche is, and covers the API's non-paging behavior, response size, and absence of search/sorting. An agent has everything needed to invoke the tool correctly and interpret the response.

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 input schema already describes both parameters completely, so the baseline is 3. The description raises this by adding the crucial caveat that pageSize and currentPage are effectively ignored because the API returns every niche in a single call—information that is not inferable from the schema alone.

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 opens with a specific action ('Use this first when the user asks about their niches') and explicitly states it 'Retrieves the Niches of the account.' It also names the key output fields, clearly distinguishing this as the account-level niche enumeration tool from the get_niche_* siblings.

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?

It states exactly when to use the tool ('when the user asks about their niches, or to find a nicheId') and names the downstream tools that require the ID. It also provides explicit negative guidance: do not walk currentPage while hasNext is true because paging is not applied.

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