guild_preflight_deep

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

Discloses the paid nature and the payment retry flow, and implies read-only behavior via 'paid read.' It does not explicitly state side effects or data retention, but the main cost/behavior is made clear.

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 mostly focused but repeats payment/x402 instructions and the 'PAID' emphasis. It remains reasonably concise given the payment-sensitive context.

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?

Describes the return categories and payment flow, but omits parameter-level guidance such as api_key usage and does not specify output fields. Adequate for orientation but not fully complete.

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 schema has zero descriptions, and the description only hints at x402_payment retry mechanics and gives an example URL. The url and api_key parameters are not meaningfully explained.

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?

Clearly states the tool evaluates endpoint safety and drift before delegation or payment, and distinguishes it from the free guild_preflight by naming the added drift and corroboration capabilities.

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?

Explicitly identifies when to use the tool ('when asking is this agent endpoint safe to call?' or when drift detection is needed) and contrasts it with the free guild_preflight, including payment retry instructions.

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