Get MFL free agents

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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false), so the bar is lower. The description adds genuinely useful traits beyond them: results are sorted by year-to-date fantasy points under the league's own scoring rules, and coverage spans offense and IDP.

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?

Front-loaded with the core purpose in one sentence, then a compact Args list. The Args block duplicates the schema somewhat, keeping it just short of maximally efficient, but nothing is padded or verbose.

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?

With no output schema, the description does the necessary work of stating what comes back: available players ordered by league-scored fantasy points. Pagination and format are covered by the schema, so an agent has enough to call it correctly; only the alternative-tool routing is missing.

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 100%, so every parameter including ranges, defaults, and the response_format enum is already documented. The Args block mostly restates schema content (limit range, offset default) without adding filter syntax or semantics beyond it, which is the expected baseline.

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 ('List players available (not on any roster) in the league') plus the sort order and scope (offense and IDP), which distinguishes it from the generic sibling mfl_get_players. It never names the sibling explicitly, so the differentiation is inferable rather than stated.

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 parenthetical '(not on any roster)' implies the use case (finding waiver-wire pickups), but the description gives no explicit when-to-use, when-not, or pointer to alternatives such as mfl_get_players. Usage is left to inference.

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