list_url_params_replace

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

Annotations declare readOnlyHint=true, and the description's verb '列出' is consistent. The additional mention of 'tab: 参数替换' gives a small UI-oriented context but does not disclose return format, pagination, or other behavioral details. This is acceptable given the simple list nature, but not rich.

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 phrase that gets straight to the point: the action and the resource. There is no wasted wording, and it is appropriately sized for such a simple 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?

With no parameters, a basic output schema, and simple list semantics, the description is adequate but minimal. It does not clarify what 'URL 参数替换' encompasses or what the output represents, leaving some ambiguity. Given the low complexity, this is a minimum viable description.

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 input schema has zero properties and schema coverage is 100%, so there are no parameters to document. The description identifies the resource being listed, which is sufficient context for a parameterless tool. Baseline for 0 params is 4, and the description does not detract.

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 verb '列出' (list) and names the resource 'URL 参数替换' (URL parameter replacement), clearly indicating a listing tool for this specific feature. However, it does not distinguish itself from sibling tools like list_url_blacklist or list_url_redirects, so it earns a 4 rather than 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 implies this tool is used to list URL parameter replacement rules, but provides no explicit guidance on when to use it over alternatives or any exclusions. For a simple list operation the context is understandable, but the lack of any alternative mention keeps it at a 3.

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