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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuinely useful context: prices and wallets live outside genesis.json, failed deliveries refund automatically, and ordinary Genesis.action cannot submit a registered paid action. Much of this describes the purchase flow rather than the read call itself, but it is real behavioral signal beyond the annotations.

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 purpose is front-loaded in the first sentence, but the body drifts into purchase-flow mechanics (purchase.completed, transactionId, payload) that are tangential to a read-only catalog call. It is dense rather than tight.

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?

No output schema and no parameter documentation, so the description should carry more of the burden. It explains the broader commerce model but never says what the read actually returns (offer shape, catalog revision form), leaving the agent under-informed about the response.

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% and the description never mentions workspaceId or liveWorldId, their formats, or their relationship. With low coverage the description is expected to compensate, and it does not.

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?

Opens with a specific verb+resource: 'Read host-owned paid Genesis offers, fixed gem prices and catalog revision.' An agent can identify what is retrieved, though the sibling set_world_commerce is never named, so read-vs-write differentiation relies on inference from the verb.

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?

There is no explicit when-to-use or when-not-to-use statement, and no reference to set_world_commerce as the mutation alternative. The surrounding prose explains how the commerce system works rather than when an agent should call this reader versus another tool.

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