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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds useful output context — that results include both tickers and books, gross edge, volume and tier, and that a Pro tier also returns resting orders, net-of-fee edge and quarter-Kelly size — which is real value beyond the annotations, though it says nothing about auth needs, rate limits, or what 'Pro'/'tier' actually means.

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?

Three sentences, front-loaded with the triggering user questions before the mechanics, with no filler. It is dense but every sentence contributes (usage, scope/outputs, Pro tier differentiation).

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 no output schema, the description correctly compensates by describing the returned fields, and all five optional parameters are fully documented in the schema. The remaining gap is the unexplained 'Pro'/'tier' concept and no sense of result ordering or pagination, but for a read-only scan tool it is largely complete.

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%: every parameter documents its default, accepted formats and clamping behavior. The description adds no parameter-level meaning beyond that (its 'net-of-fee edge' phrasing only loosely echoes min_edge, which the schema already defines), so the baseline 3 applies.

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 concrete verb and resource: scanning Kalshi college football and NFL spread/total strikes that are priced out of order for locked arbitrage, crossed-mid inversions and wide books. It is clearly more specific than a generic 'find arbitrage' tool, but it never names the siblings it is not (e.g. nfl_ladder or find_arbitrage), so an agent must infer the boundary.

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 questions — "is any CFB ladder mispriced" and "where can I make a market on Kalshi" — which map well to the tool's job. However, it offers no when-not guidance and does not route to alternative tools for the adjacent cases, so it stops short of full alternative-aware guidance.

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