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

With no annotations supplied, the description carries the full disclosure burden and does well: it states quota (100/day per caller wallet), throttling (5-second minimum interval), the behavior at exhaustion (paid challenge returned instead of a result), and that no payment is taken. It stops short of saying whether results are cached/deterministic or what happens on malformed or incomplete declaration sets.

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?

It is front-loaded with the purpose and the free-tier scope before the rate-limit and HTTP-equivalent details, and every clause conveys something operational. It is a single very dense block, though, mixing deliverable description, quota, payment semantics, and an HTTP URL without line structure.

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 10-parameter, nested-object tool with no output schema, the description supplies the missing return-value picture (verdict line, per-class counts, scope banner, fixed 12-item disclosure) and the cost/throttle model. What remains unstated is the validation success path (e.g., which of the optional documents are needed for a meaningful verdict) and whether partial submissions are accepted.

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% across all 10 parameters, so the schema already explains prm, card, asDocs, manifest, declaredRevision, selfReportedCapture and challengeObservation. The description only refers collectively to 'the same declaration set as the paid report' and adds no per-field syntax, format, or required-vs-optional guidance beyond that, 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 and resource ('Free pre-check for the MCP Auth-Surface Conformance service') and immediately defines the deliverable — signed verdict line, headline counts per class, scope banner, 12-item not-assessable disclosure — while explicitly excluding per-check grades, which is precisely what separates it from the paid auth_surface_check sibling.

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 context for when to reach for it (free tier, submit the same declaration set as the paid report, no payment/x402 challenge required) and warns that on quota exhaustion the paid challenge is returned instead. It never explicitly names auth_surface_check as the escalation path for full per-check grades, so the alternative is only implied rather than stated.

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