restore-topology-ui-config

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

With no annotations, the description must convey behavioral traits. 'Restore from a backup' implies overwriting the current configuration, but this is not explicitly disclosed. No mention of side effects, destructive potential, safety, or return value. The description is too minimal to be transparent.

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, clear sentence with no wasted words. It is well-structured and front-loaded with the verb and resource. Despite being short, it is appropriately concise for a simple operation.

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?

Given the simple nature (one param) and no output schema, the description is not fully complete. It omits important context such as whether the restore overwrites existing settings, requires prerequisites like a valid backup, or returns a confirmation. No annotations compensate. The description is minimally viable but lacks completeness.

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 schema provides a 100% description coverage for the 'config' parameter ('Configuration object from a previous backup'). The tool description itself adds no parameter semantics beyond that, so with full schema coverage, baseline 3 is appropriate.

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 a specific verb 'Restore' with a clear resource 'topology UI configuration' and source 'from a backup'. It clearly states what the tool does and, while not naming the sibling, is unambiguously distinct from the backup operation.

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, prerequisites (e.g., needing a prior backup), or alternatives. It doesn't mention that this is the inverse of backup-topology-ui-config or suggest any when/why context.

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