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

Annotations already cover read-only and open-world, so the bar is lower, yet the description still adds real value: the numbers come from each player's own Kalshi strike ladder, the tool returns prices only with no recommendation, and weekly projections are gated behind Pro. That is useful disclosure about scope and limits.

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?

Front-loads usage scenarios in quotes, then the output, then the caveats; nearly every clause carries information. The 'read off his own strike ladder' phrase is colorful but slightly opaque to an agent unfamiliar with Kalshi.

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 does the work of explaining what comes back (median per-stat pricing and anytime-TD price, compared on shared stats). It does not mention error cases such as an unmatched player name, which matters for a lookup 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 100%, so the baseline is 3, but the description adds the 2–4 player constraint and the point that players are only compared on stats they share, which shapes how the agent should batch names. Minor arithmetic gap: the count is stated but not tied to the array-or-string flexibility.

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 resource (Kalshi market pricing per player stat plus anytime-TD price) and the comparison operation across 2–4 players. It is clear what the tool returns, but it never explains how it differs from the sibling compare_players, which sounds like the same job.

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?

Gives concrete trigger phrases ('should I start Nacua or Adams', 'who does the market like more this week') and the 2–4 player bound, so an agent knows the intended context. It offers no exclusions and does not route the agent away from compare_players.

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