Manage WiFi Interface

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

Annotations already declare idempotentHint=true and readOnlyHint=false, which are consistent with the description. The description adds the constraint that at least one of disabled or ssid must be provided, but does not elaborate on behavioral traits such as what gets affected or whether changes are reversible. Given the annotations, the description provides marginal additional value.

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 extremely concise: two sentences, front-loaded with the core action. Every word is necessary and there is no filler.

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?

The description covers the main purpose and the key parameter constraint. The dryRun parameter is described in the schema but not mentioned in the description, which would be helpful for agents to know they can preview changes. However, with 100% schema coverage and no output schema, the description is still quite complete for a simple management tool.

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?

All parameters have schema descriptions (100% coverage). The description adds value by clarifying the mutual exclusivity constraint between disabled and ssid, which is not enforced in the schema. This helps the agent understand the required relationship.

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 states the resource (WiFi interface) and the specific actions (enable, disable, update SSID). It distinguishes from sibling tools, as it is the only manage tool for WiFi interfaces, and the verb-resource combination is 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 does not provide guidance on when to use this tool versus alternatives like list_wifi_interfaces or other management tools. It only mentions a validation constraint (at least one of disabled or ssid) but no context for selection.

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