qui_delete_notification_target

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

The description adds no behavioral context beyond the existing destructiveHint annotation. It does not state that the notification target is permanently removed, nor any side effects or requirements (e.g., auth). The description merely gives an invocation pattern, providing no additional disclosure beyond what annotations already convey.

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 that front-loads the endpoint and conveys the call structure efficiently. There is no unnecessary text or repetition of information already in the schema or annotations.

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 simple delete operation, the description omits critical context: it does not explicitly state that the tool deletes a notification target, nor does it specify how to provide the ID parameter. The generic argument-passing instructions are not enough to construct a valid call without assuming documentation conventions.

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?

The schema is generic (a single 'arguments' object with no specific properties), and the description only provides a general rule for placing path variables, query parameters, and body. It never explicitly states that the notification target ID must be passed as arguments.id, and the endpoint path's '{id}' is the only hint. This is insufficient compensation for the 0% schema 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?

The description names the exact endpoint (DELETE /notifications/targets/{id}), which clearly implies it deletes a notification target by ID. However, it uses 'Call' instead of explicitly stating 'Delete', and it doesn't distinguish from sibling delete tools beyond the endpoint path.

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?

There is no guidance on when to use this tool, no mention of alternatives such as qui_update_notification_target or qui_create_notification_target, and no clarifications about prerequisites or irreversible consequences. The only instruction is about how to structure the API call, not about usage context.

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