panelica_server_get_v1_server_metrics

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 useful context by stating the required scope 'server:read' and repeating 'Read-only', but it doesn't describe what metrics are returned or any behavioral caveats.

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, followed by endpoint, category, scopes, and read-only status. It is well-structured, though 'Read-only' is redundant with the readOnlyHint annotation.

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 zero-parameter read-only endpoint, the description covers invocation essentials like route and required scope. However, with no output schema and no mention of what specific server metrics are included, an agent has limited understanding of the response content.

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 the input schema is complete, so no parameter documentation is needed. The description doesn't add parameter information, but none is required 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?

The description clearly states the action and resource: 'Get server metrics' with the HTTP path GET /v1/server/metrics. It is unambiguous about what the tool does, though it doesn't differentiate it from closely related siblings like server_get_v1_server_status or metrics_get_v1_metrics_native.

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 versus alternatives such as server status or native metrics endpoints. The description provides context like category and required scopes, but no conditional or exclusionary language to help an agent choose between related tools.

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