ProofRail MCP Release Certifier

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new traits beyond them: results are cached only, the call is free, and the response may include optional x402 certification offers. It stops short of describing staleness or pagination 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?

Four dense sentences, front-loaded with the free/read-only constraint and the default-vs-query usage split. It is slightly redundant in restating read-only alongside the annotations, but no sentence is wasted.

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 7-parameter, zero-coverage tool with no output schema, the description covers the primary mode of use and hints at the return contents (certification offers) but leaves the six filtering/sorting parameters and the shape of a returned server entry unaddressed.

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 0%, so the description must carry parameter meaning. It explains the query parameter well (searched across names, URLs, repositories, and observed tool names) and implies a stability-oriented default, but sort, limit, source, min_tools, min_pass_rate, and min_observations receive no explanation at all.

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 and resource: find currently reachable public MCP servers from ProofRail's autonomous catalog, with the added scope of cached, PASS/ok candidates. The purpose is unambiguous, but no sibling (mcp_radar_snapshot, mcp_radar_changes) is named or contrasted, so an agent must infer the boundary itself.

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?

Gives explicit branching guidance: call with no arguments for the most stable current PASS/ok candidates, or supply query for task/capability search. That is clear when-to-use context, but there is no when-not-to-use and no routing to the sibling radar tools.

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?

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, covering the safety profile completely. The description adds no behavioral context beyond that – nothing about what is checked, how failures surface, or what the response means.

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?

Four words, front-loaded, no filler. It is efficient, though borderline under-specified rather than exemplary.

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 trivial zero-param probe with full annotation coverage and no output schema, the description is minimally adequate but leaves the agent guessing at the return semantics and the meaning of a non-healthy result.

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?

Zero parameters, so there is nothing for the description to document; the baseline for a parameterless tool is 4.

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?

Names a specific resource ('ProofRail process health'), which is enough to distinguish it from the other ProofRail siblings (info, certify, preflight, quotes). The verb is implicit but conventional for a health-check endpoint, so an agent can tell what it does.

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?

No guidance on when to call this versus e.g. proofrail_info or the certification tools. The agent must infer that this is a liveness/readiness probe rather than a diagnostic detail tool.

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?

Annotations already declare readOnly, idempotent, non-destructive, and non-open-world. The description adds genuinely useful context beyond them: that results are cached, that it does not trigger a live scan, and that it reflects exactly the two most recent scans. It omits pagination/limit behavior and result shape, but the annotations carry the safety profile.

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 short, front-loaded clauses with no filler. The cost and read-only facts come first and the cached-vs-live constraint follows immediately.

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 simple read-only tool this covers the essentials, but with no output schema and an eight-value enum whose meanings are never explained, an agent cannot know what each type filter actually selects. The missing parameter semantics leave a real gap.

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%, and the description says nothing about either parameter. The eight enum values (NEW, NOT_SEEN, OUTCOME_CHANGED, etc.) and the limit bound (1-50, default 20) are undocumented anywhere, so the description fails to compensate for the coverage gap.

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 ('inspect') and a precise resource ('changes observed between ProofRail's two latest autonomous MCP Radar scans'). It differentiates implicitly from mcp_radar_snapshot by noting it operates on cached results, though the sibling is never named.

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?

Gives a clear use context ('Cached results only') and an explicit when-not clause ('does not trigger a live scan'), plus a cost note ('FREE'). It stops short of naming the alternative tool (mcp_radar_snapshot) for triggering a live scan, leaving that inference to the agent.

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?

Annotations already declare readOnly/idempotent/non-destructive/openWorld=false, so the safety profile is covered. The description adds genuinely new behavioral context: results are cached and point-in-time, and calling it will NOT trigger a live scan — an important side-effect expectation. It omits pagination and result-shape details, but for a read tool that is minor.

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 compact sentences, front-loaded with the free/read-only/cached framing before the scan-vs-cache distinction. Nothing is wasted, though it could have traded a few words for parameter guidance.

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 tool with ten optional filter parameters and no output schema, the description leaves the entire query surface undocumented and gives no hint about what the response contains. The safety/behavior side is adequate, but the invocation surface is not.

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?

Ten parameters with 0% schema description coverage, and the description says nothing about any of them — not sort, query, source, outcome, or any filter. An agent must infer the meaning of every filter from its name alone, so the description fails to compensate for the coverage gap.

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 and resource: inspecting ProofRail's latest scan of public MCP endpoints drawn from public registries. It distinguishes itself implicitly from siblings like mcp_radar_changes by being a point-in-time snapshot rather than a diff, but it never names an alternative explicitly.

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 'cached, does not trigger a live scan' clause implies when this is appropriate (cheap/read-only inspection rather than a fresh scan), but there is no explicit when-to-use/when-not guidance and no sibling is named as the alternative.

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 burden well: it discloses the paid x402 flow (payment requirements/challenge, then client pays and retries the same call) and the deterministic ALLOW/BLOCK/REVIEW and PASS/FAIL/PARTIAL evidence semantics. It stops short of stating auth/permission prerequisites or rate limits, but payment behavior is unusually well documented.

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?

Purpose and the preflight alternative are front-loaded before the payment mechanics, and every sentence carries information. It is dense and somewhat packed into one long block, but nothing is redundant.

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 6-param paid tool with no output schema and no annotations, the description covers payment flow, expected evidence outcomes, and prerequisite alternatives. Minor gaps remain around permissions and return payload shape, but it is largely self-sufficient.

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%, so the schema already defines every parameter including the required_tools gate and baseline_schema_hashes drift check. The description reinforces their purpose ('require named tools', 'compare baseline_schema_hashes from a previous certification') but adds no syntax or format detail beyond the schema, so 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+resource ('MCP server verification and certification') plus the deployment contract scope, and explicitly names what distinguishes it from siblings (preflight, quote_certification). An agent can identify this as the paid certification tool without opening the 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?

Gives explicit triggers ('certification before deploy, upgrade, or trust') and names the alternatives with the condition that selects them ('Use mcp_release_preflight first for a free no-payment compatibility check, or quote_certification(target_url)'). Routing is fully specified.

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?

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), so the description only needs to add context. It contributes a genuinely non-obvious trait not present in the annotations: this call is free and produces a limited preview rather than a full paid artifact, which matters for an agent deciding whether to spend a call.

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?

A single sentence that front-loads the key differentiator ("FREE, no payment") and then lists the concrete checks. No padding, though the commercial framing ("before buying a full evidence receipt") is more marketing than operational.

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 read-only, no-output-schema tool, the description tells the agent what the call returns at a high level (reachability, protocol negotiation, tool count, schema issue count), effectively covering the missing output schema. Auth requirements and rate limits are unstated but are not critical for a preflight call.

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 the schema already documents target_url, check_profile, and declared_protocol_version. The description's enumeration of checks (reachability, protocol negotiation, tool count, schemas) largely restates the schema's own description of the "basic" profile, adding little beyond it, so the 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 (run a verification/compatibility preflight) against a specific resource (an MCP server endpoint) and enumerates what it checks: reachability, protocol negotiation, tool count, schema issue count. It is clearly distinguishable from heavy siblings like mcp_release_certify, though it never names that sibling explicitly.

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?

"before buying a full evidence receipt" and the schema note "before deployment or integration" give a clear condition for using this instead of the paid path. However, the alternative is referred to only obliquely (no tool name like mcp_release_certify), so the routing is implied rather than explicit.

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?

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is fully covered by structured data. The description contributes only the 'FREE' cost note, which is genuinely useful context annotations cannot express, but adds nothing about response content or behavior.

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?

A single compact sentence with the most decision-relevant qualifiers ('FREE, read-only') front-loaded. It is slightly redundant in repeating 'MCP verification, MCP server verification,' but wastes little space.

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?

With no input parameters and no output schema, the description is the only source of information about what comes back, and it only gestures at topics via a keyword list rather than describing the returned capability/info structure. Annotations cover the safety side, but the payload expectations remain thin.

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 tool takes zero parameters, so there is nothing for the description to document and the baseline of 4 applies. No parameter-related value is lost.

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 enumerates the topics covered (verification, preflight, certification capabilities, payment mode) rather than stating a clear verb+resource, so the agent must infer that this is an informational/capability-discovery endpoint. It does distinguish the tool's scope from siblings like health or quote_certification by topic, but the purpose is delivered as a comma-separated keyword list rather than a declarative sentence.

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?

There is no explicit guidance on when to call this versus alternatives. The sibling set includes health, find_mcp_servers, mcp_release_preflight, and quote_certification, and the description names overlapping concepts (verification, preflight, certification, payment mode) without saying which situations should route here.

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?

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the call is FREE and the response shape changes depending on whether target_url is supplied (exact buy_now action), which is not derivable from the annotations.

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?

A single dense sentence, front-loaded with the key selling point (FREE, read-only, no arguments) before the targeting detail. The colon-joined clauses are packed but nothing is wasted.

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 exists, and the description does tell the agent what comes back (price and network, or a buy_now action). However, for a 3-parameter tool with zero schema coverage, the two unmentioned parameters leave the invocation contract 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?

With 0% schema description coverage the description must carry parameter meaning, and it only explains target_url (it yields the exact buy_now action) and the omission semantics for the zero-argument case. check_profile and declared_protocol_version are left entirely undocumented, so compensation is partial.

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 and output: produce a verification/certification quote returning price and network, and optionally the exact buy_now action. The word 'quote' inherently separates it from the actionable siblings mcp_release_certify and mcp_release_preflight, though it never explicitly names them.

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 states the condition for a general quote (no arguments) versus the targeted form (pass target_url), and places usage 'before payment'. It does not explicitly exclude or route the agent away from the sibling certification/preflight tools, so it stops short of full when/when-not guidance.

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