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

The description describes an ordering/payment operation that spends $1.50 USDC and creates a brief, while annotations declare readOnlyHint=true. That is a direct contradiction of the declared safety profile, matching the 'description claims a write while annotations say read-only' failure mode.

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?

Four dense sentences, all front-loaded with the highest-value facts (what it is, price, allowed topics, latency, then the payment flow). Nothing is filler, though the payment flow sentence is long enough to be slightly heavy.

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 paid two-step tool with no output schema, the description covers price, latency, polling behavior, and the full challenge/pay/retry loop. It omits failure/refund behavior and what the delivered brief actually contains, minor gaps given no output schema.

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 100% and both parameters are well documented in the schema, so the baseline is 3. The description adds meaning beyond the schema by constraining valid topic values to five named lanes and by explaining the two-step semantics of payment_signature in workflow terms.

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 verb and resource ('Order a custom research brief on your topic'), plus scope constraints (allowed lanes) and cost. It is unmistakably distinct from siblings like check_brief_status, get_brief, or get_price.

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 routes the agent: use check_brief_status to poll (and notes polling is free), call without payment_signature first to get the challenge, pay, then call again with the signature. When-to-use and the alternative tool are both named.

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