SonarQube MCP Server

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

Annotations already provide key behavioral hints: read-only, non-destructive, idempotent, and closed-world. The description adds minimal context by specifying it's for SonarQube projects, but it doesn't disclose additional traits like rate limits, authentication needs, or what the metrics entail. It doesn't contradict annotations, but adds little value beyond them.

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 appropriately sized and front-loaded, with the core purpose stated first. The 'Args' section is structured but could be more integrated. It avoids unnecessary details, though the formatting as a code block might be slightly verbose for pure conciseness.

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 moderate complexity, rich annotations, and the presence of an output schema, the description is reasonably complete. It covers the basic purpose and parameters, and the output schema handles return values. However, it lacks usage guidelines and deeper parameter explanations, which slightly limits completeness.

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 0%, so the schema provides no parameter details. The description compensates by explaining 'project_key' as 'The project key' and 'metric_keys' as 'Comma-separated metric keys' with a default set, adding basic semantics. However, it doesn't fully clarify formats or examples, leaving gaps for a tool with 2 parameters.

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: 'Get quality metrics for a SonarQube project.' It specifies the verb ('Get') and resource ('quality metrics for a SonarQube project'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'list_projects' or 'check_status', which might also relate to project information, so it doesn't reach the highest score.

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 no guidance on when to use this tool versus alternatives. It doesn't mention sibling tools like 'list_projects' or 'search_issues', nor does it specify prerequisites or exclusions. The only implied context is for retrieving metrics, but this is too vague for effective tool selection.

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