Get Basic Settings

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

Annotations declare readOnlyHint=true, already covering the safety profile. The description adds the specific fields returned (hostname, timezone, NTP) but no further behavioral traits such as authentication needs or rate limits. With annotations present, this is adequate but not rich.

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?

A single short sentence, front-loaded with the core purpose and a brief parenthetical listing key fields. No wasted words.

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?

With an output schema present, return values need not be explained. The description lists representative fields (hostname/timezone/NTP) which orients the agent sufficiently for a no-param read 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 tool has zero parameters, so the schema is vacuous. Per rubric, zero-parameter tools baseline at 4; the description adds no parameter semantics beyond field examples, which is appropriate here.

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?

States a specific verb (获取/get) and resource (设备基础设置/device basic settings) and enumerates fields (hostname/timezone/NTP), which helps distinguish it from other settings getters like get_wifi_basic_settings. However, it does not explicitly differentiate from sibling tools such as get_system_overview or get_kernel_settings.

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 when-to-use guidance or alternatives are provided. The description only states what the tool returns, leaving the agent to infer the appropriate context for calling it among many sibling tools.

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