panelica_subdomains_delete_v1_subdomains_id

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

The description adds valuable context beyond the destructiveHint annotation by explicitly stating 'WARNING: destructive — permanently removes the resource' and 'Required scopes: domains:delete.' This communicates irreversibility and an authorization requirement that annotations do not fully cover.

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 compact and well-structured: the core action leads, followed by endpoint, category, required scope, and a clear warning. Every line carries essential information with no filler.

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 one-parameter destructive delete operation, the description covers the required scope, the irreversible nature, and the endpoint. The lack of response details is not critical since no output schema exists and the operation is straightforward.

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 single parameter 'id' is fully documented by the schema as a path parameter. The description only confirms this by showing the endpoint template /v1/subdomains/:id, adding no new semantic information beyond the schema.

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 states the exact action ('Delete subdomain') and reinforces it with the HTTP method and a warning that it 'permanently removes the resource.' This is a specific verb+resource combination that clearly distinguishes it from get/patch siblings.

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 through the verb 'Delete' and the destructive warning, but it does not explicitly state when to use this tool versus alternatives or mention any prerequisites beyond scopes. An agent must infer that this is the tool for permanently removing a subdomain.

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