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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, so safety is covered. The description adds real behavioral context beyond that: the 20,000-run simulation basis, the 80/20 market/sim price blend, and which picks are live vs paper. It stops short of stating auth or rate-limit behavior.

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-loaded with what the tool is and how it works, and every clause carries information. It is a single dense run-on sentence, though, which slightly hurts scannability versus short distinct sentences.

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 carries the return-value burden and does it well, enumerating points, win/spread/over chances, the two price columns, missing-player value, picks and the graded record with CLV. Only the 'team' and 'limit' semantics are lightly covered.

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 75%, so most parameters are already documented. The description reinforces the default 'today' view and clarifies paper ('non-published') spread/total picks, but adds little on 'team' or 'limit' beyond the schema, so baseline 3 is appropriate.

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 verb and resource: it simulates 'every NBA game today 20,000 times' and returns model points, win/spread/over chances, prices and graded picks. The NBA qualifier alongside the sim_picks family (mlb/mma/nfl/nhl siblings) makes clear which sport this covers without opening a schema.

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 notes the 'view today (default) or history' switch, which guides the parameter choice, but gives no guidance on when to reach for this tool over the many adjacent NBA siblings (projections, props, optimizer) or any prerequisites. Usage is implied rather than spelled out.

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