sleeper_trending_players

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

Annotations already declare readOnly, idempotent, open-world and non-destructive behavior, so the safety profile is covered. The description adds nothing else: no mention of defaults for lookback window or limit, no statement that results are a live trend snapshot rather than historical data.

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?

A single short sentence front-loads the resource, but the brevity is under-specification rather than economy - no sentence in it adds information an agent could not get from the tool name.

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?

Four optional parameters with no required fields, no output schema, and no defaults stated means the agent cannot know what sport, limit, or lookback window it gets by omitting them. For a trending-snapshot tool whose meaning depends entirely on those windows, this is a real gap.

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 only 25% - the lone documented parameter ('type: add or drop') merely restates its own enum. The description says nothing about 'sport', 'limit', or 'lookback_hours', which are the parameters that most affect results and which lack defaults documentation.

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 ('Get trending players') plus the platform (Sleeper), which is enough to distinguish it from sleeper_players (all players) or sleeper_nfl_state (state). It stops short of explicitly contrasting with those siblings, so 4 rather than 5.

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?

There is no when-to-use guidance, no mention of the add/drop trend distinction, and no statement of how this differs from sleeper_players. The agent must infer from the tool name alone that this is for waiver-trend style lookups.

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