list_updown_separation_rules

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

The description only says 'list', which is consistent with readOnlyHint=true, but it adds no behavioral context such as pagination, filtering, or that it returns all rules. No additional transparency 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 extremely concise (one short phrase), but it adds no information beyond the tool name. It is not verbose but does not earn its place as a useful addition.

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?

For a simple list tool with no parameters and an output schema, the description is minimal. It doesn't explain what up/down separation rules are or when to use this tool, but the name and output schema may compensate partially. Still, it lacks context about the resource or usage.

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?

There are no parameters in the schema, and the description doesn't mention any. With 0 parameters, the baseline is 4, and no further parameter info 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 '列出上下行分离规则' is a direct translation of the tool name, providing no new information. It restates the name without specifying scope or distinguishing it from sibling list tools.

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 alternatives. Many sibling list tools exist, but no criteria or exclusions are given.

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