Health check

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the tool verifies configuration and connectivity, implying a read-only diagnostic operation, but doesn't specify what happens if verification fails, whether it requires authentication, or what the output looks like. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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: 'Verify Jira MCP server configuration and connectivity.' It is front-loaded with the core purpose, has no unnecessary words, and efficiently conveys the essential information without waste, making it highly concise and well-structured.

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 diagnostic nature and lack of annotations or output schema, the description is incomplete. It doesn't explain what the verification entails, what results to expect (e.g., success/failure indicators), or how it interacts with the Jira system. For a tool that likely returns status information, more context is needed to guide the agent effectively.

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 input schema has 100% description coverage, with the parameter 'siteName' documented as 'Optional: Specify your Atlassian site name.' The description doesn't add any meaning beyond this, such as explaining when to use the parameter or its impact on the verification process. With high schema coverage, the baseline score of 3 is appropriate, as the schema handles the parameter documentation adequately.

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: 'Verify Jira MCP server configuration and connectivity.' It specifies the verb ('verify') and the target ('Jira MCP server configuration and connectivity'), making it easy to understand what the tool does. However, it doesn't explicitly differentiate from sibling tools like jira_get or jira_post, which might also involve connectivity checks indirectly.

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 prerequisites, such as whether it should be used before other operations, or contrast it with sibling tools like jira_get for data retrieval. The lack of usage context leaves the agent without clear direction on when this tool is appropriate.

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