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

The readOnlyHint annotation already establishes this as a safe read, lowering the bar. The description contributes the default value of queryType and the parameter family required for range mode, but says nothing about data retention, sampling resolution, rate limits, or auth/scope requirements.

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?

Two sentences, zero filler, with purpose followed by usage guidance. The raw REST path GET /v1/projects/{projectId}/services/{serviceId}/metrics is arguably redundant for an MCP caller and is the one element that does not earn its place.

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?

With no output schema, the description ideally would say what the metrics payload looks like (units, series shape, container grouping), and it does not. Its coverage of inputs and modes is adequate, so it is viable but leaves the return side undocumented.

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 description coverage is 100%, so all eight parameters are already documented in the schema, making 3 the baseline. The description restates the queryType modes and their companion parameters but adds no unit clarification (the schema's 'unix ms/seconds per API' ambiguity on time/startTime is left unresolved).

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?

Names a specific verb (Get) and resource (CPU / memory metrics) with explicit scope (a service's containers), which cleanly separates it from sibling readers like northflank_get_service or northflank_get_job. An agent can identify the tool without opening the schema.

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?

Gives concrete mode-selection guidance: queryType=single (default) for a current snapshot, queryType=range with duration/startTime/endTime for a time series. It does not, however, state when to call this tool versus sibling tools or any prerequisites, so it stops short of full when/when-not coverage.

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