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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so safety is covered. The description adds the 'published' qualifier and the basketball limitation, but says nothing about pagination behavior (limit/offset exist) or what the response contains. Adequate but not rich beyond the annotations.

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 short sentences, front-loaded with the core action and free of padding. The basketball note is compact and functional rather than filler.

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 described, and annotations cover the safety profile. Still, for an 8-parameter tool with zero schema descriptions, the pagination (limit/offset) and season/model parameters are unexplained, and the basketball/sport-enum mismatch is left dangling. Solid but not fully 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 0% across 8 parameters, so the description carries the full burden. It names only position, week, and scoring_format, and adds no format/default/syntax detail; season, model, limit, and offset go entirely unexplained. The sport enum even permits 'basketball' while the description says basketball is unsupported, which the description does not reconcile.

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 and resource (published weekly fantasy football rankings) plus the scoping dimensions (one position, week, scoring format). The 'weekly' qualifier implicitly distinguishes it from get_season_rankings, but no sibling is named or contrasted explicitly.

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?

'Use this for start/sit comparisons or a ranked position list' gives a use context, and 'does not support basketball' provides one exclusion. However, it never mentions the adjacent siblings (get_player_rankings, get_season_rankings, get_player_projections), leaving the agent to infer when this tool beats them.

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