Prediction-market quote

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

Annotations (readOnlyHint=true, destructiveHint=false) are reinforced and expanded: 'Read-only ... Never mutates state.' Adds details about paper trading, virtual funds, and not financial advice. Also mentions return of decisionSupport for market quality, which is additional behavioral context.

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?

Three sentences, front-loaded with purpose and outputs, then constraints. No redundant words. Every sentence earns its place.

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 5 parameters (100% schema coverage), annotations, and existence of output schema, the description covers the tool's function, key outputs, constraints, and safety warnings. Agents have enough context to invoke correctly.

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%, so baseline is 3. The description adds value by stating 'min to open is 10' for stakeMusd (beyond schema >0) and explains agentTrace as 'Optional private trace metadata stored in the caller's ledger.' This goes beyond schema descriptions.

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 it's a read-only PM quote for a binary outcome, listing key outputs (entry probability, share estimate, etc.) and differentiating from sibling quote tools by specifying 'binary outcome'. The verb 'quote' and resource 'PM' are specific.

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 explicitly says 'Never mutates state' and 'Paper trading only — virtual funds (50,000 mUSD). Not financial advice.' It also gives a condition: 'stakeMusd must be > 0 (min to open is 10).' While it doesn't explicitly say when not to use, the context and sibling tools (open_pm_position) imply use before trading. Lacks explicit alternatives.

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