listMostActiveClients

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

No annotations are provided, so the description carries full burden. It discloses the tool is read-only (Get) and describes the returned fields and sorting. However, it omits information on authorization needs, rate limits, or whether any state changes occur, which are essential for behavioral transparency.

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 two concise sentences plus a clarifying third sentence. It is front-loaded with the action and output, and every sentence adds value. No unnecessary words or repetition.

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 description covers purpose, parameters, and return fields adequately. However, it does not specify limits like the number of clients returned (e.g., top 10), which is a gap for a 'most active' query. With no output schema and many sibling tools, this information would help the agent understand the scope.

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 covers both parameters (siteId, customHeaders) with descriptions. The description does not add parameter-specific details beyond the schema, but the schema descriptions are clear (e.g., siteId fallback to default). With 100% schema coverage, a baseline 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 'Get the most active clients in a site, sorted by total traffic.' It specifies the verb (Get), the resource (most active clients), and the scope (in a site, sorted by total traffic). This distinguishes it from sibling tools like listClients which would list all clients without sorting by traffic.

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 labels it as a 'dashboard endpoint' providing a 'quick overview', implying a use case but not explicitly stating when to use it over alternatives. No exclusions or when-not-to-use guidance are provided, leaving the agent to infer context.

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