polymarket_spread

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

No annotations are provided, so the description must disclose behavior. It says returns '{spread}' but does not explain if the tool is read-only, has rate limits, or any side effects. The return format is vague (just a field named 'spread').

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 extremely short (one sentence) and front-loaded. However, it may be too terse; a bit more context would improve without harming 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 no output schema and no annotations, the description should explain the returned value, the nature of the spread (e.g., difference between bid and ask prices), and any usage context. The current description is insufficient for a financial tool.

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 0% and the description does not define the 'token_id' parameter beyond implying it's an outcome token. No hint on format (e.g., hex string, numeric ID) or how to obtain it. The description adds minimal value over 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?

Description states 'Bid-ask spread for one outcome token,' which clearly identifies the tool's purpose (retrieving spread) and distinguishes it from sibling tools like polymarket_price or polymarket_midpoint. However, it could be more explicit about the action (e.g., 'gets the bid-ask spread').

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?

No guidance on when to use this tool versus alternatives (e.g., polymarket_price or polymarket_midpoint). No mention of context, prerequisites, or when not to use. The description is purely declarative.

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