preview_create_market

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

With no annotations, the description carries the transparency burden. It clearly states the tool does NOT build a transaction, implying non-mutating behavior, and that it validates parameters. This is valuable behavioral insight, though it could also mention error handling or return details.

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?

Two sentences total: first states purpose and behavior, second gives usage direction. The critical Lab market constraint is highlighted with 'IMPORTANT.' No wasted words; all information is essential.

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?

Given the tool's simplicity and the presence of a detailed schema, the description covers the key usage and behavioral aspects. It does not describe the output format (e.g., cost breakdown, validation errors), but as a preview tool this might be inferable. The Lab market note adds necessary complexity awareness.

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%, but the description adds a cross-parameter rule tying market_type to the corresponding timing field, which is not explicitly stated in any single parameter description. This extra guidance helps disambiguate the conditional requirements for Lab markets.

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?

The description states 'Preview market creation' with a specific verb and resource, then clarifies 'validates params and shows costs WITHOUT building transaction,' which clearly distinguishes it from the many build_* sibling tools. It also explicitly references build_create_market_transaction as the follow-up, reinforcing its unique role.

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 advises 'Use before build_create_market_transaction,' giving direct sequential context. The IMPORTANT note about Lab markets ('you MUST provide market_type and the corresponding timing field') offers concrete when-to-use guidance beyond generic descriptions.

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