show_qryrdsl

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

With no annotations, the description fully carries the behavioral burden; 'read-only' is a useful safety disclosure. However, it does not describe what the returned line info contains, whether data is current, or any error/empty-result behavior, so transparency is only partial.

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?

One front-loaded sentence conveys operation, subject, and safety trait with no filler. It is appropriately minimal for a parameterless query tool.

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 low complexity (no parameters, no output schema, no annotations), the description contains the essential information needed to select and invoke the tool. 'ADSL/VDSL line info' adequately signals the return substance, and 'read-only' covers the safety profile.

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 baseline is 4; no parameter documentation is needed. The schema coverage is effectively 100% because the properties object is empty, and the description correctly adds no parameter information.

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 names a specific verb ('Query') and a concrete resource ('ADSL/VDSL line info'), and the parenthetical 'read-only' makes the operation unambiguous. This sets it apart from the large set of generic show_* and sys_* siblings.

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 gives no guidance on when to use this tool versus related status/query siblings such as show_traffic, wan_status, or show_status. The only usage signal is implied by the subject 'ADSL/VDSL line info'.

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