get_available_players

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It covers authentication needs (ESPN_S2 and SWID cookies for private leagues), environment variable fallbacks, defaults, and the return format (list of player dictionaries with auction values and rankings). This provides meaningful transparency, though it omits potential errors or rate limits.

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 well-structured with a one-sentence purpose, an Args section, and a Returns section. It is appropriately sized for 5 parameters, with no redundant information or filler. Every sentence contributes to understanding the tool.

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?

Given the tool's moderate complexity (5 optional parameters, env var fallbacks, auth requirements), the description is complete: it explains purpose, all parameters, defaults, authentication, and return values. The presence of an output schema further reduces the need to detail return structure, and the description adequately covers behavioral context for an agent to invoke the tool correctly.

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?

The input schema has 0% description coverage, but the description fully documents all 5 parameters with clear semantics: ESPN league ID, season year, limit, and authentication cookies. It also explains env var fallbacks and defaults, adding substantial meaning beyond the raw schema.

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 begins with a specific verb+resource: 'Get top available players for the draft with auction values.' This clearly states what the tool does and differentiates it from sibling tools like get_free_agents or get_trending_players by focusing on draft context and auction values.

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 implies usage for draft preparation and provides contextual details (e.g., optional league_id, env var fallbacks), but it does not explicitly state when to use this tool versus alternatives like get_free_agents or get_trending_players, nor does it mention exclusions. Usage context is implied rather than explicit.

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