wireless-list-ssids

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

The description mentions '(read-only)', which is a behavioral trait indicating no modifications. However, there are no annotations to support this, and the description does not disclose other behaviors like pagination, rate limits, or authentication requirements. It adds minimal transparency beyond the read-only note.

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 very concise (one sentence plus a note) and front-loaded with the key action. It uses minimal words effectively, but could potentially include a bit more context without becoming verbose.

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?

Given the tool's simplicity (list SSIDs with optional fields) and lack of output schema, the description is modestly complete. It misses details on return structure and pagination, but for a list tool with 100% schema coverage, it is adequate but not thorough.

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 the baseline is 3. The description does not add any meaning beyond what is already in the schema. It does not explain the parameters or their usage, so it does not improve parameter understanding.

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 identifies the resource ('MR SSIDs') and the action ('List'), and adds context with '(read-only)'. It effectively states what the tool does, distinguishing it from sibling tools like wireless-get-ssids which likely retrieves a single SSID.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of scenarios, exclusions, or when not to use it. Given many sibling list tools, the lack of usage context is a gap.

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