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

With no annotations, the description carries the full burden and does well: it discloses the operation sequence (handshake, info capture, tool listing, grading) and the output shape (0-100 score, letter grade, per-tool detail). It stops short of stating safety profile (read-only vs. mutating), timeout/network-failure behavior, or rate limits.

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?

Front-loaded with the verb and the enumerated operations, followed by the use case. Every clause earns its place; the grading-detail list is dense but directly informs the agent about scope and output.

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?

No output schema and no annotations, yet the description specifies the returned artifacts (score, grade, per-tool detail) and the pipeline of steps, which is enough to call it correctly. It omits failure modes and latency expectations, a minor gap for a network probe.

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?

Only one parameter and schema coverage is 100%, so the schema already documents 'url' fully with an example. The description's phrase 'remote MCP server' adds minor framing but no format or constraint detail beyond the schema — 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?

States a specific verb (probe) and resource (remote MCP server), then enumerates the exact steps — initialize handshake, server info, protocol version, tool listing, quality grading. Nothing else in the sibling set does anything similar, so an agent can distinguish it immediately.

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?

Explicitly says to use it 'to vet an MCP server before connecting an agent (or paying per call) to it,' giving a clear use context. It does not name a when-not condition or an alternative, though no close sibling alternative exists to route away to.

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