explain_checkExplain one agent-readiness check in depth: what it is, why it matters for AI agents and AI search, exactly how the scanner tests it, what counts as a pass, and the official sources. Call with no check_id to list every check.
| Name | Required | Description | Default |
|---|---|---|---|
| check_id | No | The check's id, as shown in a scan report (e.g. "dnsAid", "aiCrawlerAccess"). Omit to list all checks. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds genuine context beyond that by disclosing the shape of the returned explanation (definition, rationale, test method, pass criteria, sources), which is valuable given there is no output schema.
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 sentences, no filler. The purpose and the content of the explanation are front-loaded, and the behavioral instruction for the no-argument case follows immediately. Every clause earns its place.
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, read-only lookup tool with no output schema, the description is nearly self-sufficient: it says what it explains and what the explanation includes, and annotations carry the safety profile. Only a note on what happens with an invalid or unknown check_id 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 description coverage is 100% and the check_id parameter is fully documented in the schema, including the enum and the instruction to omit it. The description's "call with no check_id to list every check" largely restates the schema rather than adding new semantics, so the baseline of 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 names a specific verb (explain) and a specific resource (one agent-readiness check), and even enumerates the five things the explanation covers. It is trivially distinguishable from the sibling scan_website, since one explains a single check while the other runs a scan.
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 clear operational guidance for the optional parameter: "Call with no check_id to list every check," which tells the agent exactly how to use the tool in the no-argument case. It does not explicitly state when to prefer this over scan_website or what to do with a returned explanation, but the usage context is unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.