remove_wireless_access_list_entry

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

The description adds a behavioral caveat that the function is legacy and behaves differently in RouterOS v7.x, which goes beyond the annotations. However, it does not explain the nature of the differences or any side effects. Given annotations already mark destructiveHint and idempotentHint, this is some additional context but still limited.

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 one short sentence, but it is under-specified rather than concise. It fails to convey essential information and reads more like a placeholder warning than a useful tool description. No structure or front-loading of purpose.

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 is incomplete for a destructive tool: it does not explain what the operation does, what the version differences are, or any prerequisites or consequences. The schema is minimal, and the description adds little to make the tool usable. The output schema exists but is not used to compensate.

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 input schema has two parameters (device, entry_id) with no descriptions, and schema description coverage is 0%. The description provides no parameter information, so the agent gets no help understanding the meaning or usage of these parameters.

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 ('Legacy function - different in RouterOS v7.x') does not state what the tool does. It only provides a legacy/version warning, with no verb+resource. The tool name and title imply removal of a wireless access list entry, but the description itself is missing a purpose statement.

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 guidance on when to use this tool vs alternatives. The note about being different in RouterOS v7.x could hint at version-specific usage, but it does not explicitly say when to use or avoid this tool. The description offers no clear context or alternatives.

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