panelica_logs_delete_v1_logs_logrotate_name

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

Annotations already carry destructiveHint=true, and the description adds concrete context by warning 'destructive — permanently removes the resource' and stating the required scope logs:write. This goes beyond the structured fields and clarifies the consequence of calling the 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?

Every line is useful: the action, the HTTP verb/path, category, required scope, and the destructive warning. It is compact, front-loaded, and contains 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 simple one-parameter delete operation, the description covers the essential details: what is deleted, the HTTP endpoint, authentication scope, and irreversibility. It does not mention response codes, but with no output schema and a straightforward delete this is a minor gap.

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 coverage is 100%, and the single parameter 'name' is documented as 'Path parameter: name'. The description's endpoint path echoes this without adding deeper semantic meaning, such as the format or purpose of the name value. The schema carries the burden here.

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?

Description states the specific action 'Delete logrotate config' with the HTTP method and exact endpoint path. The delete verb plus resource clearly distinguishes it from sibling logrotate tools like get, post, put, rotate, and test.

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 HTTP DELETE method and the verb 'Delete' make the operation obvious, but there is no explicit when-to-use guidance, exclusions, or mention of alternatives. The description implies usage rather than stating that this is for removing an existing logrotate config that should first be listed with panelica_logs_get_v1_logs_logrotate.

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