list_custom_url_library

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

The readOnlyHint annotation already declares a read-only operation, and the description adds the tab context as minor behavioral context. No mention of pagination, sorting, or data scope, but the output schema likely covers return values. The description is consistent with the annotation, so no contradiction.

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 in Chinese, efficiently stating the tool's purpose. It is front-loaded and contains no filler, though it is minimal and could be slightly more informative.

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 read-only list tool with no parameters, an output schema, and a readOnlyHint, the description is adequately complete. It clearly identifies the resource, and the surrounding sibling context confirms it is one of many CRUD operations. It could mention that it returns the full list or any sorting, but these are likely in the output schema.

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?

With zero parameters, there is no need for the description to explain parameter semantics. The input schema is empty, and the baseline of 4 applies because there is nothing to compensate for.

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 uses the specific verb '列出' (list) with the resource '自定义网址库' (custom URL library), clearly indicating a list operation. It distinguishes from sibling tools like add_custom_url_library and delete_custom_url_library by the verb, though it does not explicitly mention alternatives.

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. The only additional context is the tab name '自定义网址库', which hints at a UI location but does not explain use cases, prerequisites, or exclusions.

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