get_ipv6_line_detail

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

The annotation readOnlyHint=true already discloses that this is a safe read operation. The description adds no further behavioral context (e.g., whether it queries live data, required permissions, or response structure). Since annotations cover the primary safety profile, a neutral score is appropriate, but the description adds zero value beyond the annotation.

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, efficiently worded sentence that directly states the purpose. There is no fluff, repetition, or unnecessary detail. Every word earns its place.

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 tool is a simple getter with no parameters and an output schema, so the description doesn't need to explain return values. However, it lacks contextual completeness in differentiating this from other IPv6 getter tools. Given the sibling list, an agent might struggle to know exactly what 'line detail' means versus 'config' or 'WAN/LAN config'. The description is adequate but not rich enough to fully resolve ambiguity.

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 and the schema coverage is 100%, so the baseline for this dimension is 4. The description correctly includes no parameter explanations because there are none. It does not add any extra semantic detail, but none 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 '获取 IPv6 线路详情' clearly states the tool's function: retrieving IPv6 line details. It uses a specific verb and resource, and the tool name itself distinguishes it from siblings like get_ipv6_config, get_ipv6_wan_config, and get_ipv6_lan_config. However, it does not explicitly contrast with these alternatives, so it stops short of a 5.

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 guidance on when to use this tool versus its siblings. Given the existence of several IPv6-related getters, an agent needs more context to confidently choose this specific tool. No exclusions or alternative references are provided.

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