listClientsActivity

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value by describing the return shape (per-snapshot counts of new, active, and disconnected clients split by EAP vs switch), but it says nothing about default time window behavior, pagination, or sampling granularity.

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 short sentences, front-loaded with the core action and scope. The final sentence largely restates the earlier 'activity statistics over time' framing, so there is minor redundancy but nothing bloated.

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 must carry the return-value burden, and it does so by enumerating the metrics per time snapshot. For a read-only, three-optional-parameter tool this is close to sufficient; only default time-range behavior and the granularity of snapshots are left unstated.

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 description coverage is 100% and all three parameters (start, end, siteId) are documented in the schema with units and defaults. The description adds no further parameter meaning — it never mentions the time range or site scoping — so the baseline of 3 applies.

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 gives a specific verb and resource ('Get client activity statistics over time from the dashboard') and even narrows the payload to new/active/disconnected clients across wireless and wired. It does not, however, contrast itself with close siblings such as listMostActiveClients, getClientsDistribution, or getPastClientNum, so an agent still has to infer the boundary.

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?

'Useful for monitoring client connection trends and activity patterns' implies the monitoring use case but never states when to pick this over the many other client-statistics siblings, nor any exclusions or prerequisites. Usage is implied rather than directed.

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