cvcue_delete_ssid

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

There are no annotations, so the description must carry the behavioral burden, and it does disclose the key failure mode (template reference) and the write-gate/confirm requirements. It does not state irreversibility explicitly, whether this is a hard or soft delete, or what happens to devices or clients currently using the SSID. Solid but incomplete for a destructive operation with zero annotation coverage.

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?

Three short sentences, front-loaded with the action, then failure mode, then preconditions. No filler. The inline GET path is slightly dense but functional.

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 two-parameter destructive tool with no output schema, the description covers the action, the blocking dependency, and the auth/confirm gates an agent needs to succeed. The remaining gap is downstream impact on devices referencing the SSID, which matters for an agent deciding whether the delete is safe.

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 both parameters are already documented, and the description mostly restates the confirm requirement already present in the schema. Marginal added meaning beyond the schema, consistent with the baseline for full coverage.

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 an SSID profile"), which separates it from cvcue_get_ssid and cvcue_list_ssids by operation. It does not name a sibling explicitly, but the destructive verb plus the SSID-profile resource makes the scope unambiguous.

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?

Gives concrete preconditions for use: CVCUE_ENABLE_WRITES=true and confirm=true, plus the blocking condition that the profile must not be referenced by a device template. It even points at the check endpoint to verify that first. It lacks only a general statement of when to prefer alternatives (e.g. removing a device reference instead of the profile).

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