post_wifi_config_reset

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

No annotations are provided, so the description carries full burden. It fails to disclose whether the tool performs a destructive reset or a creation. The word 'Crate' (typo for 'Create') contradicts the 'reset' in the name, creating confusion. No mention of side effects, permissions, or idempotency.

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 contains a list of error codes that distracts from the main purpose. The purpose is not front-loaded; it starts with a vague statement. Every sentence should add value, but the error codes are not explained in context.

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 (6 params, nested objects, output schema exists), the description is insufficient. It does not explain what the tool does (reset vs create), what the output contains, or how the error codes relate to the operation. The schema coverage is high but the description adds little context.

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 6 parameters with complete descriptions (100% coverage). The description does not add any additional meaning beyond what the schema already provides; it only lists error codes unrelated to parameters. Baseline of 3 is appropriate.

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 says 'Crate a new the WifiMacFilter' which is grammatically poor and vague. It suggests creating a Wi-Fi MAC filter, but the tool name 'post_wifi_config_reset' implies resetting configuration. This mismatch reduces clarity. No specific verb-resource pair is clearly stated.

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 like 'post_wifi_mac_filter'. The description does not mention context, prerequisites, or scenarios where this tool is appropriate.

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