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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so the safety profile is covered. The description earns credit by inventorying the return payload in detail, which matters because no output schema exists, and by clarifying that trading is external. However, it doesn't say how many 'most recent' buys/sales/claims are returned or whether the probability history is truncated, so the payload volume is still unbounded for the agent.

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?

Purpose is front-loaded in the opening clause and the two trailing sentences carry the id-source and no-trading guidance. The field enumeration is long but nearly all of it substitutes for a missing output schema; a slightly tighter list would improve it.

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?

With one required parameter fully documented, annotations covering the safety profile, and a detailed return-value inventory standing in for the absent output schema, the agent has what it needs to call this correctly. The only gap is unbounded/undefined sizing of the recent-trades and probability-history sections.

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%, including a pattern and a concrete example id, so the schema does the heavy lifting and baseline 3 applies. The description goes slightly beyond by naming the source tool for the id and reinforcing the id-based lookup, which helps the agent populate the field correctly.

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 ('One Bodega prediction market by its id') and then enumerates the exact data returned: question, YES/NO probability, shares outstanding, funds, volume, deadline, outcome, probability history and recent trades. That makes it unmistakable against the sibling list_prediction_markets, which returns many markets rather than one.

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?

Explicitly tells the agent how to obtain the required id ('Get the id from `list_prediction_markets`') and adds a when-not clause: trading cannot be performed here, `tradeUrl` points to the actual market on Bodega. Both the selection path and the out-of-scope action are named.

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