SonarQube MCP Server

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

Annotations already declare this as read-only, non-destructive, idempotent, and closed-world. The description adds useful context about pagination behavior (1-indexed page, 1-500 page size) and filter syntax (comma-separated values), but doesn't mention rate limits, authentication needs, or what happens when filters return no results.

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 efficiently structured with a brief purpose statement followed by parameter documentation. Every sentence adds value, though the formatting as a bullet list could be more front-loaded with key usage information before parameter details.

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 has annotations covering safety profile and an output schema exists (so return values needn't be explained), the description provides adequate context. It fully documents all parameters and their semantics, though could benefit from more behavioral context about error cases or performance characteristics.

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% schema description coverage, the description carries full burden for explaining parameters. It successfully documents all 8 parameters with clear semantics: project scoping, filter options (severities, types, statuses, tags, assignment), and pagination details including valid ranges and defaults. This fully compensates for the schema gap.

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 searches SonarQube issues with filters, providing a specific verb ('search') and resource ('SonarQube issues'). However, it doesn't explicitly differentiate from sibling tools like 'get_issue' or 'list_projects', which could also retrieve issue-related information.

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 like 'get_issue' (for single issues) or 'list_projects' (for project overview). It mentions filtering capabilities but doesn't specify use cases or prerequisites for effective searching.

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