put_wifi_ap_id

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

No annotations are provided, so the description must disclose behavioral traits. It only lists error codes without explaining side effects, permissions, or operational impacts. The error codes hint at possible failures but lack explanation.

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 short but the error code list is long and poorly formatted. It starts with the clear statement but then dumps a raw list. While concise, it sacrifices structure and readability.

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 complexity of the input schema (nested objects, many parameters) and presence of an output schema, the description should provide an overview of what the update does, which fields are modifiable, and any constraints. It only says 'Update the WifiAp' and lists error codes, which is insufficient.

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 schema already describes parameters. The description adds a list of error codes not in the schema, providing some extra context. However, it does not elaborate on parameter semantics or relationships.

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 'Update the WifiAp', specifying a verb and resource. It distinguishes from sibling tools like put_wifi_config or put_wifi_bss_id by focusing on the AP itself. However, it lacks further context about what exactly is updated, but the purpose is clear.

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?

No guidance is provided on when to use this tool versus alternatives such as put_wifi_config or put_wifi_bss_id. The description does not explain the context or prerequisites for updating a WifiAp.

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