panelica_logs_post_v1_logs_clear_all

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

The description states 'Mutating: changes server state,' which is consistent with readOnlyHint=false, but the operation itself — clearing all logs — is destructive and irreversible, directly conflicting with destructiveHint=false. The description also fails to warn that all log data is affected globally. This is an annotation contradiction.

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 short, front-loaded with the action, and includes endpoint/scopes/mutation facts without rambling. Minor redundancy ('Mutating: changes server state' restates what readOnlyHint=false already implies) keeps it from a 5.

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 destructive operation with no output schema, the description should stress irreversibility and global scope. It only says 'Clear all logs' and 'mutating,' leaving the agent unaware of the full impact and of the relationship to sibling clear/truncate tools.

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 there are no required parameters, so the baseline is 3. The single 'body' parameter is described only as an open arbitrary JSON object ('Schema not statically declared'), and the description adds no further meaning; however, a clear-all call plausibly requires no body.

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 opening phrase 'Clear all logs' names a specific action and resource, and the description adds the HTTP endpoint and category. It is clear enough to identify the operation, but it does not state the precise scope of 'all logs' (global vs account-level) or explicitly differentiate from sibling tools like panelica_logs_post_v1_logs_clear_id and panelica_logs_post_v1_logs_sites_id_clear.

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 gives a prerequisite ('Required scopes: logs:write') but no guidance about when to choose this tool over related log-clearing or truncation tools. No alternatives or exclusions are mentioned, so the agent must infer selection from the name alone.

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