League Rosters with Draft Info

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description adds no further behavioral context (e.g., no mention of data freshness, pagination, or that it combines two endpoints). The description is consistent but adds minimal value 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?

The description is a single, efficient sentence. It is front-loaded and has no wasted words. However, it could include a brief note about combining roster and draft data without harming conciseness.

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 output schema exists, explanation of return values is not needed. However, the tool combines two data sources (rosters and draft info), and the description does not mention this aggregation. It is minimally complete but lacks context about its composite nature relative to siblings.

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?

With 0% schema description coverage, the description should compensate by explaining the league_id parameter. It does not add any meaning beyond the schema's type and name. The agent must infer that league_id identifies the league, which is trivial but still a gap.

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 retrieves all rosters with draft-position metadata per player, using a specific verb and resource. It distinguishes from siblings like 'get_league_rosters' (just rosters) and 'get_league_draft' (draft info alone), making its unique value obvious.

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 when to use (when both roster and draft metadata are needed) but offers no explicit guidance on when to avoid it or which sibling alternative to choose (e.g., 'get_league_rosters' if only rosters are needed). No exclusions or context conditions are provided.

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