cvcue_ssid_usage

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

No annotations exist, so the description carries the full burden. It does usefully disclose that the call is a GET (read-only) and that the data is live rather than historical, but it says nothing about freshness/staleness, pagination, or whether the counts are instantaneous or averaged.

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 front-loaded sentence plus an endpoint parenthetical, with zero filler. The reader learns the data domain and the return fields in two lines.

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 only two optional parameters and no output schema, the description does the main remaining work: it enumerates the fields the caller gets back (broadcast status, bands, AP/client counts). It falls short of fully describing return structure or aggregation semantics, which matters slightly given no output schema exists.

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%, so both parameters (active_only, location_id) are already documented in the schema. The description's mention of 'which SSIDs are broadcast' lightly reinforces active_only, and 'per SSID/WLAN' scoping aligns with location_id, but it adds no new meaning such as how the location subtree filter interacts with AP/client counts.

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 resource and verb: live per-SSID/WLAN monitoring data, enumerating broadcast SSIDs, bands, and AP/client counts. It also names the underlying endpoint (GET /manageddevices/aps/wlans). It does not explicitly contrast with sibling cvcue_list_ssids or cvcue_get_ssid, so an agent must infer the config-vs-usage distinction.

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?

Usage is implied by 'live monitoring data' and the usage-count framing, which suggests this is for observing current SSID deployment rather than reading SSID configuration. There is no explicit when-to-use statement, no exclusions, and no pointer to cvcue_list_ssids for the configuration view.

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