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

Annotations only declare the generic write profile (readOnly=false, idempotent=false, destructive=false), so the description carries real weight: it discloses that this 'changes live host pricing,' that availability:live grants signed-in viewer access during an active stream, that fulfillment:video reserves payment asynchronously, and that benefits are granted only on purchase.completed. 'Replace' mildly tensions with destructiveHint=false, but this is a nuanced recoverable update rather than a clear contradiction.

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?

Purpose and prerequisites are front-loaded, then offer semantics, then behavioral caveats. Sentences are dense and jargon-heavy but almost all carry distinct information; there is minor redundancy in restating availability/fulfillment meanings that the schema's const values already imply.

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 complex, 5-parameter mutation with no output schema and thin annotations, the description covers prerequisites, offer structure, pricing rules, availability/fulfillment behavior, and explicit non-goals. Missing only explicit scope of what 'replace' overwrites and confirmation of the return/refresh behavior.

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 0%, so the description must compensate and largely does: it explains the revision pair to pass, that each offer binds a declared actionId with fixed payload and optional inputFields, and that gem prices must be whole values. It leaves workspaceId/liveWorldId unexplained, but names are self-evident and the offer object semantics are well covered.

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: 'Register or replace paid Genesis offers' for a world, which is clearly a write counterpart to the read-only get_world_commerce sibling. It could be sharper about the world/live context, but an agent can identify the operation without opening the schema.

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?

Gives explicit prerequisites ('Read get_world_commerce and get_world_experience first. Pass both current revision fields'), which is strong just-in-time routing. It also bounds scope with 'does not purchase or start generation,' but does not state when this should be preferred or skipped beyond those reads.

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