cisco_backup_diff

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

With no annotations, the description carries the full burden and does disclose the non-obvious stateful behavior — that the tool persists snapshots per device and behaves differently on first vs. subsequent calls. It omits auth requirements and rate/return details, but the baseline/diff disclosure is genuinely valuable.

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?

Two tight sentences with the core action front-loaded and the baseline caveat following. No filler; every clause earns its place.

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?

An output schema exists, so return structure needn't be described. Between the schema (param) and the description (stateful behavior and drift semantics), an agent has everything needed to invoke it correctly.

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 single 'device' parameter is already documented as the inventory router/switch name. The phrase 'for the same device' reinforces that identity matters, but adds no new syntax or format meaning. Baseline 3 applies.

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?

States specific verbs (Fetch, diff) and resources (Cisco running configuration vs. last snapshot), plus the outcome ('flags unexpected config drift'). An agent can distinguish this from cisco_backup or cisco_interfaces without opening the schema.

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?

Explains the stateful call sequence clearly: the first call establishes a baseline, later calls diff against it. That is strong contextual guidance, but it never names when to prefer it over the sibling cisco_backup, so it stops short of explicit alternative routing.

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