sleeper_trending_players

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

Annotations already indicate readOnlyHint and idempotentHint, so the bar is lower. The description adds useful behavioral context: return format (top-level array), semantics of 'count' (how many leagues made the move), need to resolve player_id via a roster or player file, and that no auth is required. No contradiction with 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?

The description is reasonably concise and well-structured with clear sections: purpose, return format, example, auth. However, the final line 'Also answers this: espnfantasy_player_info.' is confusing and seems out of place, slightly detracting from clarity.

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?

For a simple read-only tool with no output schema, the description covers the essential context: return format, count semantics, player_id resolution, authentication, and an example. It does not mention pagination or limit behavior, but the schema covers parameters. The odd cross-reference line slightly reduces completeness.

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% with clear descriptions for all four parameters (limit, sport, add_or_drop, lookback_hours). The description's example shows a typical call but adds no additional meaning beyond what the schema already provides. 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 clearly states the tool's function: 'Players being added or dropped most across all of Sleeper'—a specific verb+resource with scope ('across all of Sleeper'). It distinguishes itself from the player file download and sibling Sleeper tools by focusing on trending/waiver-wire signals.

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?

The description gives an example and implies usage as a waiver-wire signal ('without downloading the 15 MB player file'), but it does not explicitly state when to use this tool over other Sleeper tools or when not to use it. The reference to 'esPNfantasy_player_info' is ambiguous and does not serve as a clear alternative comparison.

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