delete_device

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation profile is known. The description adds genuinely non-obvious behavior — device_name matching is fuzzy — which is important for a destructive call, but it omits what happens on an ambiguous match or a miss, and whether the operation is undoable.

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 sentence with zero filler; the destructive action is front-loaded before the selection mechanism. The parenthetical '(fuzzy)' is the only detour, and it 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 values need no explanation, but this is an irreversible mutation over an ambiguous name-based selector. The definition should say how ambiguity or a missing device is handled and what track_type governs; without that it is only minimally sufficient.

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 0%, so the description must carry the load; it does explain that device_index and device_name are alternatives for identifying the device and adds the fuzzy-match semantics for names. However, track_type (defaulting to 'track', plausibly track/return/master) is never explained, and there is no precedence rule for supplying both device_index and device_name.

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 ('remove') and resource ('device or plug-in'), plus the container it lives in ('from a track') and the two ways to identify the target. An agent knows exactly what is deleted, though nothing explicitly distinguishes it from siblings like delete_track or move_device.

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, when-not-to-use, or alternative routing is given. The description never says when to prefer this over delete_track, or when to select by index versus name; the '(fuzzy) name' hint describes the matching mode but not the decision rule.

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