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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds valuable context beyond them: Pro authentication via PredictionMarketsPicks or a Pro API key, and the ticket fields the caller receives. It does not discuss rate limits or unmodeled-ticker behavior in prose, though the schema covers the latter.

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 dense and front-loaded, moving from use cases to output shape to watchlist mode to auth. It earns most of its length, though the long middle sentence listing ticket fields could be tightened.

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?

For a read-only tool with no output schema and only two parameters, the definition is complete: it explains what the tool returns, how to use the optional watchlist parameter, and the authentication prerequisite. Nothing an agent needs to call it correctly is missing.

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 parameter documentation is already strong. The description adds only marginal guidance—pass tickers[] for a watchlist and commodity is needed for a real answer—which largely mirrors the 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 states a specific resource and output: the Kalshi commodity strike with the largest PMP model edge, returned as a ticket with side, entry price, resolve criterion, model probability, edge, tier, and quarter-Kelly size. This clearly distinguishes it from generic calculator/board siblings like calculate_ev or perps_board.

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?

It gives explicit trigger phrases ("gold edge today", "oil or bitcoin trade signal") and explains the watchlist mode via tickers[]. It does not name a sibling alternative or state when not to use it, so it stops short of the top score.

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