Get a Bopster market

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

With no annotations, the description carries the full behavioral burden. It helpfully discloses data semantics — amounts in USDC base units (6 decimals) and times in unix seconds (UTC) — and that positions are only included when a wallet is supplied, but it says nothing about read-only nature, behavior on an unknown/invalid address, or response size.

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?

A single dense sentence, front-loaded with the purpose and followed by the return fields and unit conventions. Every clause carries information; nothing is redundant or padded.

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?

Because there is no output schema, the field enumeration and unit conventions are essential and present. The only gap for a simple two-parameter read is the lack of any error/not-found behavior, which is minor but not negligible.

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 100%, so both parameters are already documented in the schema, establishing a baseline of 3. The description echoes the optional-wallet behavior but adds no format or edge-case detail beyond what the schema's patterns and descriptions already say.

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?

States a specific verb and resource — fetch the full detail of a single Bopster prediction market — and constrains it to lookup by on-chain address. It also enumerates exactly what comes back (question, category, source, pools, phase, oracle state, optional positions), which separates it cleanly from list_markets.

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 phrase 'single ... by its on-chain address' implies this is the point-lookup counterpart to a listing tool, but no sibling is named and there is no explicit when-not guidance. An agent can infer the usage but must do the routing itself.

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