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

Annotations already declare readOnlyHint and idempotentHint, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: coverage varies by league and era, only resolved historical observations are returned, and model-only observations are included.

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 the core purpose in the first sentence, which is good, but the middle paragraph is clause-heavy and somewhat redundant ('full available normalized projection archive' vs 'broader research dataset'). It is not wasteful enough to be a problem, but not tight.

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?

An output schema exists, so return values need not be explained. The description adequately characterizes the dataset's scope and coverage caveats, but for a 12-parameter tool with zero schema coverage and no param documentation, it leaves the invocation surface largely unexplained.

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?

There are 12 parameters at 0% schema coverage, and the description documents none of them (team, limit, cursor, market, player, result, date ranges, quality, decision, min_edge_pp). It only gestures at 'decision' via the model-only mention; the agent gets no format or filter semantics for the rest.

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 (query) and resource (normalized projection archive), and explicitly contrasts itself with the public resolved-pick ledger and the sibling get_player_prop_history. However, with several history siblings (get_pick_history, get_premium_history) it only disambiguates against one, so it's clear but not fully differentiated.

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 a clear context for use ('broader research dataset') and an explicit alternative with a selection condition: per-player NFL/MLB/WNBA prop history routes to get_player_prop_history. It does not address the other history siblings, so it stops short of full when/when-not guidance.

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