blockrun_polymarket_read

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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true. The description adds valuable context: 'without signing or changing anything', and for preview specifically 'never accepts confirm and never signs or submits an order.' No contradictions.

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?

Front-loaded with main purpose, then organized into bullet-point actions. Some redundancy in preview action details but overall well-structured and not overly verbose.

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 all key aspects: tool purpose, usage guidelines, behavior, parameter usage rules, and sibling tool differentiation. No output schema but not required for a read-only tool. Complete for an agent to use 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 has 100% description coverage with clear parameter descriptions. The description adds context for preview action (e.g., market buys use amount_usd; limit orders use price+size), which helps agents understand parameter usage beyond the schema.

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 reads or previews Polymarket state without signing or changing anything, and lists three specific actions (positions, orders, preview) with brief explanations. It distinguishes itself from the sibling tool blockrun_polymarket for write operations.

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?

Explicit guidance: use this tool for read-only operations; use blockrun_polymarket for setup and funds-affecting operations. The preview action is also clearly described as never accepting confirm or submitting an order.

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