set_wireless_passphrase

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

The annotations already mark the operation as non-destructive and idempotent, so this description only needs to add context. It adds the useful behavior that leaving authentication_types unset keeps the current setting, and it clarifies the exact RouterOS interface family. It does not discuss side effects or access requirements, but those are covered by the annotation profile.

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 main action is front-loaded in a single specific sentence, followed by one compact note about a non-obvious parameter. There is no repetition of schema or annotation information and 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?

An output schema exists, so return-value behavior does not need to be described. However, the definition leaves three parameters under-specified and does not route the agent away from sibling tools, making it adequate but not fully complete for a 4-parameter configuration 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?

Schema description coverage is 0%, so the description must compensate, but it only explains authentication_types (format, example, and unset behavior). Name, device, and passphrase receive no semantic detail beyond their property names; name could be mistaken for an SSID rather than an interface name.

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 states a concrete action and target: it sets the WiFi passphrase on a RouterOS v7 /interface wifi or wifiwave2 interface. This is clearer than the title, but it does not explicitly differentiate itself from sibling tools such as set_wireless_security_profile or update_wireless_interface.

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?

There is no explicit guidance on when to choose this tool over security-profile-based or interface-update alternatives. The phrase "directly on a RouterOS v7 wireless interface" hints at the distinction but never states exclusions or alternative tool names.

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