Get MFL league transactions

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

Annotations already declare readOnly, idempotent, non-destructive, open-world, so the safety profile is covered. The description adds genuinely non-structured context: results are rendered in plain English with resolved player names and decoded draft picks, and that `count` caps total output. It does not discuss pagination or truncation behavior beyond the count cap.

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, then a compact arg list, then two examples — each section earns its place and there is no filler. The arg list duplicates the schema somewhat, which keeps it from a perfect score.

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 zero-required-parameter, read-only query tool with rich annotations and a fully documented schema, the description covers purpose, filters, output format, and result rendering. With no output schema, the note about plain-English rendering and decoded draft picks fills the main gap; remaining omissions (pagination, empty-result behavior) are minor.

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 all seven parameters are already documented in the schema, and the description's arg list largely restates that (enum values, count range, defaults). The examples do add a little semantic value by showing how `franchise` accepts a team name and how filters combine, but the baseline of 3 applies when the schema carries the load.

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 opens with a specific verb and resource ('Get recent league transactions') and enumerates the transaction categories it covers (trades, adds/drops, waivers, IR, taxi). It also notes the output is 'plain English, with player names and decoded draft picks,' which is a real distinguishing trait. It stops short of naming which sibling (e.g., mfl_get_free_agents) to use instead for overlapping queries.

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?

Two worked examples map natural-language questions ('Any trades this week?', 'What has Team X added lately?') directly onto argument combinations, which is strong usage guidance for an agent. There is no explicit when-not-to-use statement or pointer to a sibling for free-agent lookups, so it falls short of a 5.

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