create_prediction_market

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

With no annotations, the description must fully disclose behavior. It mentions AI resolution and web sources but omits critical details such as that it deploys an on-chain contract, any required authorization, side effects, or what happens upon invocation. The use of generic terms like 'advanced' and 'sophisticated' adds little behavioral clarity.

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 description is a single sentence that effectively communicates the core action ('Create') and key features. While the adjectives 'advanced' and 'sophisticated' add fluff, the structure is front-loaded and efficient, earning a high but not perfect score for conciseness.

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 complexity of a creation tool with six parameters and no output schema, the description lacks essential context. It does not specify the result of creation (e.g., returns a contract address), deployment implications, or the lifecycle of the market. This gap leaves the agent without a complete picture of the tool's effect.

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?

All six parameters have descriptions in the schema (100% coverage), so the description adds no new parameter-level information. The description's mention of web sources aligns with the `web_sources` parameter, but does not enhance meaning beyond the schema. Baseline 3 is appropriate.

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 clearly states that the tool creates an advanced prediction market contract with specific features like AI-powered resolution and web sources. It distinguishes itself from sibling tools which focus on adding principles or generating other contract components, making its purpose explicit.

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?

The description does not explicitly state when to use this tool versus alternatives or provide usage context. However, the verb 'Create' and the detailed schema imply it is intended for defining a new prediction market, offering a moderate implicit guidance but lacking explicit when-to-use or when-not-to-use advice.

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