sros_set_delete

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

No annotations are provided, so the description carries the full disclosure burden. It implies destructiveness ('Removes the config subtree') but says nothing about commit/datastore semantics, reversibility, required permissions, or idempotency — all critical for a config-deleting gNMI Set operation.

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 short sentences plus a compact example; the destructive action is front-loaded and nothing is wasted.

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 annotations and no output schema, the description adequately conveys what happens and the path format, but omits the error/failure behavior and commit semantics an agent needs to safely invoke a destructive Set operation.

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 coverage is 100%, so the baseline is 3, but the description goes beyond it by giving a concrete YANG path literal for 'paths' (with list-key predicates like router-name=Base), which materially clarifies the expected path syntax that the schema only calls 'List of YANG paths'.

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 a specific verb and resource ('Delete configuration on Nokia SR OS via gNMI Set') and clarifies scope with 'Removes the config subtree at the given path(s).' The verb 'delete' also cleanly separates it from siblings sros_set_update and sros_set_replace without needing to name them.

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?

No when-to-use or when-not-to-use guidance is given. The description never mentions sros_set_replace or sros_set_update, so the agent must infer from the verb alone whether deletion or replacement semantics apply. Usage is only implied by the tool name.

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