Open prediction-market position

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

Discloses behavioral traits: mock/paper trading, no financial advice, idempotency, minimum stake, server-flag gating. No annotations provided, so description carries full burden. Could mention mutability.

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?

Concise and front-loaded with purpose. Every sentence adds value, though slightly dense. Could be more structured with breaks for readability.

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?

Covers many aspects but missing return value description (no output schema). Adequate for basic use but incomplete without response format.

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?

Only covers stakeMusd and idempotencyKey semantics; three other required parameters (source, slug, outcomeExternalMarketId) are not explained beyond their names despite low schema description coverage (20%).

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 'Open a mock prediction-market position (binary outcomes only)' with specific verb and resource, distinguishing it from siblings like open_futures_position and pm_quote.

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?

Provides explicit guidance on scope requirement, idempotency key requirement, minimum stake, user confirmation, and server-flag gating. However, lacks explicit comparison to alternatives for when not to use.

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