runJsonRpcCompliance

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating safe operations. Description adds the list of error cases but does not disclose additional behavioral traits like execution duration, prerequisites (e.g., server must be running), or error handling beyond the listed cases.

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 sentence that front-loads the main purpose, but it omits critical parameter details. It is efficient but incomplete, which reduces its helpfulness.

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?

Despite having 2 parameters (one complex) and no output schema, the description provides no insight into return values, success/failure indicators, or side effects. It is insufficient for an agent to fully understand the tool's behavior without additional documentation.

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%, yet the description provides no explanation of the complex 'target' parameter (stdio vs http connection) or the 'specVersion' enum. The agent must rely entirely on the JSON schema, which is detailed but lacks natural language guidance.

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?

Description clearly specifies the tool runs a JSON-RPC 2.0 compliance suite targeting an MCP server, listing specific error cases. It distinguishes itself from sibling tools (e.g., runTransportSuite, runToolSchemaValidation) which cover other aspects of testing.

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?

Usage context is implied by the tool name and description but no explicit guidance on when to use versus alternatives, nor any prerequisites or exclusions. The sibling tools are different test suites, so the purpose is clear but not comparative.

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