Answers the domain-binding challenge: the platform fetches the well-known path this draft's status already names (domainChallengeWellKnownPath) on the declared URL's host and checks it serves back the exact domainChallengeToken. Serve that token at that path on your domain BEFORE calling this. Requires the access code.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | ||
| accessCode | Yes |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Beyond the annotations (idempotent, non-destructive), the description reveals the internal check behavior and the authentication requirement. It also warns that the token must be served beforehand, which is a behavioral precondition not encoded in 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?
The description is only three sentences and packs the purpose, mechanism, and prerequisite into a compact structure. Every sentence adds value, with no redundancy.
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 tool has no output schema, so the description should clarify what a successful or failed check returns, but it does not. The id parameter is also under-specified. While the core mechanism is explained, these gaps prevent full contextual completeness.
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 coverage, the description must explain both parameters. It explicitly names 'access code' but never directly describes the 'id' parameter, only alluding to 'this draft's status.' This leaves the id ambiguous and obliges the agent to infer its meaning.
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 states the tool 'answers the domain-binding challenge' and explains the validation mechanism, clearly differentiating it from the endpoint challenge sibling. It names the specific resource (domainChallengeWellKnownPath) and token, making the purpose unambiguous.
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 provides explicit instructions to serve the token before calling and notes the access code requirement, giving clear operational context. However, it does not explicitly state when to prefer this over the sibling endpoint challenge tool, so alternatives are not fully specified.
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.