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

Annotations only cover readOnlyHint and openWorldHint, but the description adds substantial behavior: the uniform not_found semantics, the HTTP 402 / x402 PaymentRequirements flow, payTo being the member's own address on Base and Solana, the PAYMENT-SIGNATURE/X-PAYMENT headers, and the reminder to show the human price and promise before paying. This is well beyond what annotations provide.

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 lookup purpose, and the return shape is given compactly. The payment-flow detail is dense and arguably heavy for a read tool, but each sentence serves a real caller need, so only minor trimming is warranted.

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 no output schema, the description documents the return object in detail (ok, handle, count, offerings fields, how_to_pay) and covers the downstream payment mechanics. Nothing an agent needs to call it or interpret the result is missing.

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 100% and there is only one parameter, whose schema already documents the handle format. The description restates 'Args: { handle }' without adding syntax or format meaning beyond the schema, so baseline 3 applies.

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+resource+scope: 'What one Immersive Commons member sells, by handle', and enumerates the return shape. An agent can immediately tell this is a per-handle offerings lookup, distinct from siblings like ic_member_card_get or ic_donate.

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?

Clarifies exactly which offerings are returned (listed and on sale) and that unknown handle, empty member, and private member all collapse to not_found. It also explains the purchase path (GET/POST x402_url). It does not explicitly name an alternative sibling to use instead, but the context is clear.

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