mcpcheck

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

With no annotations, the description carries the burden. It discloses that remote servers are live-connected and analyzed for tool-poisoning and capabilities, checks the backing repo, and returns a score with grade. It does not mention failure modes or rate limits, but it reveals the key live-connect action, which is important.

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 well-organized: main purpose first, then accepted inputs, then behavior, then usage instruction. Every sentence adds necessary information and there is no filler.

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?

The description covers the return value, accepted inputs, and remote behavior, which is enough to call the tool. However, it is ambiguous about how registry names and GitHub repos are processed (only remote servers are said to live-connect), leaving a gap in the behavioral model.

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 already documents the three accepted target formats with 100% coverage, and the description repeats them without adding new syntax details. It adds some context by noting that remote servers trigger live connection, but this is more behavioral than semantic.

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 checks if an MCP server is safe to install and returns a trust score, with a specific verb and resource. It does not explicitly contrast with the sibling scan_mcp_server, so it lacks explicit sibling differentiation, but the purpose is unmistakable.

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?

It gives an explicit usage directive: 'Call BEFORE installing or recommending any MCP server.' This is clear when-to-use context. It does not mention scan_mcp_server or state when not to use this tool, so it falls short of full exclusion/alternative guidance.

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

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

With no annotations, the description carries the behavioral burden and it does disclose what the scan evaluates and that it is a pre-connect, inspect-style action. It remains vague about operational behavior such as whether the scan makes network calls, whether it can execute any tool logic, or what a result looks like.

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?

Two tight sentences front-load purpose and capabilities with no filler; the sibling note is compact and adds context without bloating the description.

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?

For a single-parameter security scanner this is reasonably scoped, but there is no output schema and no hint of the returned report shape or side effects. The relationship to check_mcp_trust is mentioned but not resolved, leaving an important decision point incomplete.

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% and the schema already explains target as a registry name, GitHub repo, or remote MCP URL. The description restates these accepted formats without adding syntax details or constraints, so it stays at the baseline.

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 names a specific action ('scan and inspect an MCP server for security issues') and enumerates concrete capabilities such as live tool-poisoning analysis, the exposed-tool inventory, TLS, and repo trust signals. It does not, however, differentiate scan_mcp_server from its sibling check_mcp_trust beyond saying they share the same engine.

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?

It clearly frames when the tool is useful ('before connecting it') and states the accepted target forms. It falls short of explicit selection guidance: since check_mcp_trust is described only as the same engine, an agent cannot tell which tool to prefer in a given situation.

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