v1_agent_preflightChecks whether an agent workflow is ready to execute by validating its manifest and returning preflight readiness status through a paid x402 route.
Is this agent workflow ready to execute? (PAID $0.25)
Remote route: POST /v1/agent/preflight (0.25 USD x402/base/usdc on eip155:8453).
| Name | Required | Description | Default |
|---|---|---|---|
| manifest | No | ||
| requestId | No |
| Name | Required | Description | Default |
|---|---|---|---|
| status | No |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds genuinely useful context beyond the annotations: a fixed $0.25 cost, x402/USDC payment on eip155:8453, and the POST route. However, annotations declare readOnlyHint=false, so something is being written or mutated, and the description never explains what that non-read side effect is, nor any auth/payment failure 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?
It is short and front-loaded, but the first sentence is a verbatim repeat of the title and the price appears twice (title and body). The remaining content is dense and 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?
An output schema exists, so return values need not be described, but the description leaves critical gaps: the untyped 'manifest' payload, the ordering role of requestId, and the meaning of a non-read-only preflight are all unexplained. For a paid, open-world tool this is under-specified.
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 manifest parameter has no declared type or structure at all, yet the description says nothing about what a manifest must contain. The description does not compensate for the coverage gap in any way.
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 asks "Is this agent workflow ready to execute?" which implies a readiness/preflight check on an agent manifest, but it never states a concrete verb+object result (validate? score? attest?). It also fails to distinguish itself from close siblings such as v1_preflight, v1_quota_preflight, v1_budget_preflight, or v1_readiness_attest.
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 indication of when to call this versus the many other preflight/readiness siblings, nor any prerequisite or exclusion. The only selection signal offered is the price and route, which is not usage guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.