aruba_get_rogue_aps

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

No annotations provided. Description omits behavioral details such as pagination, rate limits, or whether the list is complete. Only states 'Get list' without further elaboration.

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?

Description is very short, which helps conciseness, but it is too brief to adequately inform tool use. It front-loads the purpose but sacrifices necessary detail.

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 low complexity, the description fails to explain return format or any caveats. It is incomplete for confident invocation.

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%. The parameter 'limit' is not explained in the description, despite being the only parameter. Agent receives no guidance on its semantics (e.g., default behavior, max values).

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?

Description clearly states 'Get list of unauthorized/rogue access points' with context '(Security)'. Verb and resource are specific, and it distinguishes from siblings like aruba_get_ap_database or aruba_get_ap_stats.

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. No prerequisites or context for usage are provided.

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