espnfantasy_transactions

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

Annotations already cover read-only, open-world, and idempotent behavior. The description adds valuable context: auth requirements ('works without a key; ESPN_FANTASY_COOKIE unlocks more if set') and the return shape. This goes beyond the structured data without contradicting it.

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 compact and well-structured: purpose, return format, example, and auth note. Each section serves a purpose with no filler. The front-loaded purpose sentence is immediately informative.

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?

Despite lacking an output schema, the description provides the return structure, an example, and auth notes. It's sufficient for a read-only list tool, though it doesn't mention potential pagination or error behaviors. Overall, it's a complete enough description for the tool's simplicity.

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 the baseline is 3. The description adds a usage example with default parameter values but doesn't introduce new semantics beyond what the schema already provides for parameters like game, leagueId, or scoringPeriodId.

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 states 'Completed transactions (adds, drops, trades, waiver claims) for a scoring period', clearly identifying the resource and scope. This distinguishes it from the sibling tool espnfantasy_pending_transactions by explicitly saying 'Completed'.

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 clearly implies when to use this tool: for completed transactions in a scoring period, and provides a concrete example. It doesn't explicitly name alternatives (like espnfantasy_pending_transactions), but the 'Completed' qualifier makes the usage context unambiguous.

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