SonarQube MCP Server

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

The description adds context about what the tool returns (server version/status), which is useful beyond the annotations. Annotations already cover read-only, non-destructive, idempotent, and closed-world hints, so the bar is lower. The description doesn't contradict annotations and provides some behavioral insight, but lacks details like error handling or rate limits.

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 a single, clear sentence that front-loads the key action ('verify connectivity') and outcome ('return server version/status'). There is no wasted verbiage, and it efficiently conveys the essential information without redundancy or fluff.

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 the tool's low complexity (0 parameters, annotations provide safety hints, and an output schema exists), the description is sufficiently complete. It explains what the tool does and what it returns, and with the output schema handling return values, no additional detail is needed. However, it could slightly improve by mentioning it's a health check tool relative to siblings.

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?

With 0 parameters and 100% schema description coverage, the schema fully documents the lack of inputs. The description doesn't need to add parameter details, and it appropriately focuses on the tool's purpose without redundancy. A baseline of 4 is applied since no parameters are present, and the description efficiently avoids unnecessary information.

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 tool's purpose with specific verbs ('verify connectivity' and 'return server version/status') and identifies the resource (SonarQube). It distinguishes from siblings by focusing on connectivity/status rather than issues, projects, or rules. However, it doesn't explicitly contrast with sibling tools in the description text.

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 implies usage for connectivity verification and status checking, which suggests when to use it (e.g., for health checks). However, it doesn't provide explicit guidance on when to use this versus alternatives like checking project metrics or issues, nor does it mention any prerequisites or exclusions.

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