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

Beyond the annotations, the description discloses meaningful behavioral traits: it never connects to the server, never repeats a secret-looking value (only names its location), returns an Ed25519 signed receipt, and is a paid endpoint (0.10 USDC per call via x402 plus a 10-call free tier) requiring an X-Wever-Wallet-Proof header bound to the exact arguments. These are exactly the operationally relevant facts an agent needs before invoking it.

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 purpose and check list are front-loaded, but the definition is dense and over-long, folding in payment mechanics, a wallet-proof header, a contract path and a human page URL. Several of these earn their place, yet the paragraph runs together checks, billing and non-actions with no structure, making it easy to skim past the omission constraints.

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 two parameters, no output schema and a read-only annotation set, the description covers everything needed: what input shapes are accepted, which defects are reported, what the tool explicitly will not do, the authentication/payment requirement, and the shape of the return (signed report). Nothing essential to a correct call is missing.

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 coverage is 100%, so both parameters are already documented. The description restates the accepted shapes (mcpServers/servers map, remote url+headers entry, local command/args/env entry) almost verbatim from the schema description, adding little meaning beyond it. Baseline 3 applies.

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 opens with a specific verb and resource: 'check an MCP server configuration before you add it to a client.' It then enumerates exactly what is checked (no server name, non-HTTPS URL, credentials in address, empty/placeholder auth header, secret-looking values), so an agent can distinguish this from sibling rails like wever_mcp-diligence-rail without opening any schema.

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 when-to-use condition ('before you add it to a client') is stated explicitly, and the description also gives a when-not in effect: it evaluates the supplied config only and never connects to the server. It does not name an alternative tool or state what to do if the config fails, so it stops short of full routing guidance.

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