getDashboardMostActiveSwitches

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the sort criterion (traffic volume), but omits how many switches are returned, whether a top-N cap applies, and what time window 'most active' covers — meaningful gaps for a ranking tool.

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?

A single well-formed sentence with the resource and the sort criterion front-loaded and no filler. Nothing could be removed without losing meaning.

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?

This is a simple read with one optional parameter, so low complexity keeps the bar modest. However, with no output schema, the description should say what a returned entry looks like (switch identity plus traffic figures) and how the ranking is bounded; neither is present.

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%: siteId already documents the pattern, the OMADA_SITE_ID default fallback, and the listSites discovery path. The description adds nothing beyond the schema, so the baseline 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?

States a specific verb ('Get') plus resource ('most active switches') and adds the ordering criterion ('sorted by traffic volume'). It implicitly distinguishes itself from getDashboardMostActiveEaps and getDashboardSwitchSummary by resource and metric, though it never names those 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?

The description gives no when-to-use context, no exclusions, and no pointer to alternatives such as getDashboardSwitchSummary or listDevices. The only usage hint is the word 'Dashboard' in the name, which the description does not reinforce.

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