post_wifi_ap_id_neighbors_scan

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

No annotations provided, so description carries full burden. It discloses the action but does not describe side effects, duration, or return behavior beyond listing error codes. The error codes list lacks context on when each occurs.

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?

Very short and front-loaded with the action. The error codes list is somewhat cluttered but not overly long. Efficient, though could be more structured.

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 no output schema and simple parameters, the description lacks key contextual details such as what the tool returns (e.g., results of scan, job ID) and how to interpret the scan results. Incomplete for an agent to fully understand the 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?

The description mentions 'given ap', which directly implies the parameter 'id' is the access point identifier. With schema coverage at 0%, this adds meaning beyond the schema. However, it does not explicitly state that the parameter is the AP ID.

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 'Launch a wifi scan on given ap' clearly states the action (launch a wifi scan) and the resource (given ap). It is specific and distinguishes from sibling tools like get_wifi_ap_id_neighbors.

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 on when to use this tool versus alternatives (e.g., get_wifi_ap_id_neighbors). No prerequisites or exclusions mentioned. The description only states the action.

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