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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the mutation profile is covered; the description adds meaningful context on spending approval, target eligibility, and ticket confidentiality. The gap is that the payment mechanics of the signed checkout (capture timing, refunds, duplicate-order risk given idempotentHint=false) are not described.

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?

Front-loaded with the core action, then eligibility exclusions, then required confirmations and the privacy instruction. Four dense sentences, no filler or repetition.

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?

With an output schema present, return values need no explanation, and the description covers eligibility, exclusions, approval, and confidentiality well. It stops short of describing what the caller should do after receiving the ticket or how repeated calls behave, which matters for a non-idempotent ordering tool.

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 coverage is already 80%, and the description adds real meaning beyond the schema: targetUrl must be an authorized public HTTPS target, notes must not contain confidential data, and the enum's requiresScopeApproval members are carved out as ineligible. It does not add syntax detail for publishTarget, which is minor given the schema describes it.

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 compound action: creating a private ticket plus a signed Base USDC/ETH checkout, scoped to eligible automated services. The verb+resource is unambiguous and unlike sibling read/listing tools such as list_services or check_service_order.

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 states when NOT to call it — services with requiresScopeApproval (SaaS security, Microsite Launch) and paymentTiming:after-verified-delivery (Verified Repo Fix) — and routes those to their published manual-approval page. It also states the preconditions (authorized public HTTPS target, operator spending approval).

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