panelica_logs_get_v1_logs_logrotate_summary

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds 'Required scopes: logs:read' which is useful context beyond the annotations, and confirms HTTP method and read-only nature. It does not contradict annotations, but it provides little additional behavioral detail such as return format or aggregation scope.

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 front-loaded with the core purpose 'Logrotate summary', followed by minimal metadata lines. It has no fluff, though much of the content repeats structured fields like the title, endpoint, and annotations. It is concise but not maximally information-dense beyond structured data.

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 zero parameters, no output schema, and a simple read-only GET operation, the description provides the essential invocation details: method, path, category, required scope, and read-only nature. It lacks a description of what the summary contains or return shape, but for a trivial no-argument read-only call this is sufficient for an agent to select and invoke correctly.

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 tool has zero parameters and schema coverage is 100%, so the schema leaves nothing undocumented. The description does not need to elaborate on parameters; the baseline for a zero-parameter tool is 4, and the description adequately supports that.

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 a specific resource and operation: 'Logrotate summary' with HTTP GET to /v1/logs/logrotate/summary. It clearly indicates this returns a summary for logrotate, distinguishing it from sibling tools like the detailed logrotate listing or rotation settings. However, it does not explicitly differentiate itself from similar log summary endpoints.

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 provides context (Category: Logs, Required scopes: logs:read, Read-only) but no guidance on when to use this tool versus alternatives such as panelica_logs_get_v1_logs_logrotate or logs_sites_id. There is no 'use this when...' or 'instead of...' guidance, leaving the agent to infer when summary data is appropriate.

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