delete_device

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

No annotations provided, so the description must disclose behavioral traits. It notes 'or hide', which hints at a nuance, but fails to clarify the difference, reversibility, side effects, or permissions. This is insufficient for a mutation tool.

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 sentence, front-loading the action. Every word is necessary, with no redundancy or fluff.

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 tool's action (delete/hide), two optional parameters, and the existence of an output schema, the description is too brief. It does not explain the difference between delete and hide, nor the constraint that exactly one of idx or name should be provided. The 'hide' variant is left ambiguous.

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 compensate. It states 'by IDX or Name', indicating that either identifier can be used, which adds value. However, it does not explain what each parameter expects (e.g., idx as integer ID, name as device name) beyond the schema's basic types.

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 clearly states the action ('Delete (or hide)') and the resource ('device'), with identification method ('by IDX or Name'). This distinguishes it from sibling tools like rename_device or update_device_value.

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 implies usage for removing or hiding a device, but lacks explicit guidance on when to use delete vs hide, or any exclusions/alternatives. No prerequisites or context on which sibling tools to prefer.

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