routeinfo

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

The description explicitly states '只读' (read-only), which is a key behavioral trait. However, with no annotations provided, the description carries full burden and fails to disclose other important behaviors such as error handling, permission requirements, or side effects. The minimal addition of read-only gives it a moderate score.

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 sentence that front-loads the purpose. It contains no unnecessary words. However, its brevity sacrifices completeness, and the use of Chinese may reduce accessibility for non-Chinese agents.

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 has no output schema and only 2 parameters. The description does not specify what the output format is or how the tool behaves with different inputs (e.g., invalid port). It leaves significant gaps for the agent to understand the full behavior.

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?

Schema description coverage is 0%, meaning the schema itself lacks descriptions. The tool description does not explain the purpose or format of the 'port' and 'targets' parameters beyond what is in the schema structure. The agent receives no additional semantic value.

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 clearly states the tool queries routing information for multiple target machines, with the verb '查询' and resource '路由信息'. It also indicates read-only nature. However, it does not explicitly differentiate from sibling tools like isfile or list_targets, though the resource is distinct.

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 vs alternatives. It does not mention any preconditions, exclusions, or scenarios where other tools would be preferred.

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