nacos_rollback_config

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

With no annotations, the description does carry real behavioral weight: it discloses that the operation is atomic, that it overwrites and republishes using the full snapshot text, and that this avoids long-text transport. However it omits permission requirements, whether the rollback is itself reversible, and the effect on the current live config beyond 'overwrite'.

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 dense sentence with the action, the input key, and the mechanism front-loaded; every clause earns its place. Minor density from the parenthetical, but no filler.

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 destructive mutation with no annotations and no output schema, the description covers what happens and why it is safe from a text-transport standpoint. It leaves gaps on prerequisites (does the snapshot still exist? does it apply to the same group/namespace?), failure behavior, and confirmation/irreversibility.

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 100%, so the baseline is 3. The description adds one useful clarification about historyId's role — the full snapshot body is fetched from it so no content needs to be passed — but says nothing extra about group, namespaceId, or the dataId/historyId pairing.

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?

Names a specific verb+resource (回滚配置 / roll back config) plus the exact selecting key (historyId) and the target state (指定历史版本), which clearly separates it from nacos_publish_config and nacos_get_config_history. It stops short of explicitly differentiating itself from siblings, so it is clear but not sibling-routing.

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?

Usage is only implied: the agent must already hold a historyId, which suggests a prior nacos_get_config_history call, and this is the tool to use when reverting rather than editing content. No explicit when-to-use / when-not-to-use or named alternative (e.g. nacos_publish_config) is given.

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