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

With no annotations, the description carries the full burden, and it does disclose one important trait: without payment_reference the tool returns payment requirements rather than executing work, and payment is in Base USDC. It does not cover authorization requirements, idempotency, what happens on an invalid payment reference, or whether target_scope/payer_address change behavior. Useful but incomplete for a no-annotation tool.

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 tightly packed sentences with the payment flow front-loaded immediately after the opening. The only waste is the near-tautological first clause, 'Request a service.'

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 five-parameter tool with no annotations and no output schema, the description leaves major gaps: four undocumented parameters, unstated auth/payment failure behavior, and no sense of what a successful non-payment call versus a paid call returns beyond the payment-requirements case.

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% across five parameters, so the description must compensate. It explains only payment_reference (a confirmed transaction hash); offer_slug, target_scope, payer_address, and authorization_attestation are left entirely unexplained in both schema and description.

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 opening sentence, 'Request a service,' largely restates the tool name (request_service) and title, adding little on its own. The second sentence does reveal the real behavior, a two-step USDC payment handshake, which clarifies the actual purpose. However, it never differentiates from siblings like quote_task or list_offers, so an agent must infer where this fits.

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 two-sentence flow effectively states the invocation pattern: call without payment_reference to receive payment requirements, then retry with the confirmed transaction hash. That is clear, actionable guidance on the first vs. second call. It lacks any explicit when-not or alternative routing (e.g. when to use quote_task first), which keeps it short of a 5.

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