pm_create_market

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

No annotations are provided, so the description carries full burden. It mentions 'Create' indicating a write operation but lacks details on permissions, destructiveness, rate limits, or side effects. The image constraint is noted, but overall behavior is minimally disclosed.

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 concise with two sentences, front-loading the main action. However, it is overly terse; adding more relevant details without increasing verbosity would improve utility.

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 13 parameters, no output schema, and no annotations, the description is severely incomplete. It does not address required parameters, default values (e.g., private_event default true), or post-creation behavior. The tool's complexity demands more thorough documentation.

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 only 15% (only 'image_file_path' has a description). The description adds the constraint 'Provide image_url OR image_file_path' but does not explain other critical parameters like name, symbol, outcomes, end_time, etc. The description fails to compensate for the low schema coverage.

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 the tool creates a 'private' prediction market with metadata, distinguishing it from the sibling 'create_market' which likely creates public markets. The verb 'Create' and resource 'private prediction market' are specific and unambiguous.

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 implies use for private markets but does not explicitly state when to prefer this over alternatives like 'create_market' or 'pm_buy'. No exclusions or context for when not to use are provided.

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