get_wifi_advanced_settings

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

The description is a literal translation of the tool name and adds no behavioral context beyond what the readOnlyHint annotation already provides. With annotations present, the bar is lower, but the description still fails to disclose what 'advanced settings' include, any prerequisites, or return characteristics beyond relying on the output schema.

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 a single, concise phrase with no unnecessary words. It is front-loaded and immediately communicates the tool's purpose. Perfectly sized for a parameterless getter.

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 tool's simplicity (no params, readOnlyHint, output schema present), the description is nearly complete. However, it does not clarify what distinguishes 'advanced' from 'basic' Wi-Fi settings, leaving the agent to rely on the sibling tool name and output schema. Slight gap in contextual clarity.

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 zero parameters, so there is nothing to describe. The rule for 0 params is baseline 4, and the description correctly provides no irrelevant parameter information. Schema coverage is 100% vacuously, so no compensation is needed.

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 '获取 Wi-Fi 高级设置' translates to 'Get Wi-Fi advanced settings', which is a specific verb+resource statement. It clearly identifies the tool as a read operation for advanced Wi-Fi settings and implicitly distinguishes it from siblings like get_wifi_basic_settings by specifying 'advanced'.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. However, the name and description imply usage when advanced Wi-Fi settings are needed, which is sufficient for a simple getter. No exclusions or alternative tool references are given.

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