list_parameter_catalogs

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

The annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so the safety profile is covered. The description adds a genuinely non-obvious interpretive caveat — that a catalog version does not imply the test device model is already matched — which prevents a likely mis-inference from the returned data.

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?

A single compact sentence whose main clause (what is listed) comes first and the caution second — correctly front-loaded. Nothing is redundant, though the brevity borders on under-specification rather than optimal density.

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 an output schema present and no parameters, the description does not need to explain return values, and annotations cover safety. What is missing is the relationship to sibling catalog/parameter tools, which matters in a list of ~45 similarly named tools; the description alone does not resolve that choice.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline applies. No parameter meaning is contradicted or left ambiguous.

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 states a specific verb and resource ('列出发布包提取的参数目录' – list parameter catalogs extracted from release packages), which is clearer than the bare tool name. It does not, however, distinguish this from the closely related sibling discover_device_parameter_catalog, so an agent still has to infer which one enumerates release-derived catalogs vs device-derived ones.

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?

There is no explicit when-to-use guidance or named alternative, only an implied framing that this enumerates release-package catalogs. The caveat about catalog version is a usage caution rather than a routing rule, so the agent is left to infer the boundary against discover_device_parameter_catalog and search_parameters.

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