espnfantasy_pending_transactions

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

Beyond the readOnly/idempotent annotations, the description discloses key behavioral details: the return key is ABSENT (not empty) when no pending transactions exist, and cookie-based auth unlocks more data. These are not visible in annotations and provide valuable operational context.

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-organized into purpose, return shape, example, and auth. Every sentence conveys a distinct piece of information with no redundancy or fluff.

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 no output schema, the description explains the top-level return shape (pendingTransactions array and its absence behavior). However, it does not describe the structure of individual pending transaction items, leaving a gap for agents needing item-level details. Still, for a list-type read tool with good annotations, it is reasonably complete.

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 coverage is 100%, so the baseline is 3. The description adds a concrete example call with realistic values for game, seasonId, leagueId, and scoringPeriodId, demonstrating parameter usage beyond the schema's basic definitions. This example aids an agent in constructing a valid request.

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 explicitly identifies the resource as 'Pending/unprocessed transactions' and further specifies 'waiver claims and trade offers awaiting processing.' It distinguishes from sibling espnfantasy_transactions by the 'pending/unprocessed' qualifier, making the purpose unambiguous.

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 includes a use-case example ('Outstanding waiver claims / trade offers') and mentions auth prerequisites ('needs the private cookie in most leagues') and behavior without a key. It does not explicitly name alternates like espnfantasy_transactions, but the contrast is implied by 'pending/unprocessed.'

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