listMostActiveClients

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

With no annotations, the description carries the full burden. It discloses the sorting basis, the returned fields, and the dashboard-oriented nature, and 'get' implies a read-only operation. However, it does not mention ordering direction, pagination, limits, or behavior when no clients exist, leaving some gaps.

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 tight sentences with no filler: the main action and sort are front-loaded, followed by return fields and a concise use-case note. Every sentence adds value.

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?

For a simple one-parameter list endpoint, the description covers the core behavior and return fields, but it leaves parameter semantics ambiguous and does not state whether siteId is mandatory. Given no annotations and no output schema, it is adequate but not fully complete.

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 0% and the description never explicitly describes siteId, the sole parameter. 'In a site' hints that siteId identifies the site, but the description does not clarify whether it is required, optional, or how it is validated. The description therefore fails to compensate for the schema's lack of parameter documentation.

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?

Clearly states it gets the most active clients in a site, sorted by total traffic, and enumerates the returned fields. This distinguishes it from sibling tools like listClients (full list), getClient (single client), and listClientsActivity (activity log), making its purpose unambiguous.

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 frames this as a dashboard endpoint for a quick overview of top clients by traffic, giving the agent clear context for when to use it. It does not explicitly name alternatives or state when not to use it, but the intended use case is reasonably clear.

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