Transactions for a scoring period

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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering the safety profile. The description adds useful context about the content (FAAB amounts, claim outcomes) but does not disclose behavioral traits such as result ordering, pagination, or coverage of default periods beyond the schema defaults.

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?

Two sentences, front-loaded with the core action and scope, followed by a practical use case. Every sentence earns its place and there is no wasted wording.

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 partial return-value disclosure (FAAB amounts, success/failure) and the annotations cover read-only safety. It is complete enough for a straightforward filtered-list tool, though it leaves minor gaps around output ordering and manager identifiers.

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?

Input schema coverage is 100%, so the schema fully documents all four parameters. The description adds no new parameter-level meaning beyond broadly referencing scoring periods and transaction types, so the baseline of 3 is appropriate.

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 uses a specific verb ('Get') and resource ('roster transactions') with concrete subtypes (waiver claims, free-agent adds, drops, trades) and distinctive output details (FAAB bid amounts, claim success/failure). This clearly separates it from siblings like get_activity and get_teams without requiring schema inspection.

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 explicitly states when to reach for this tool: 'Use this to see what the waiver market paid for a player and which managers are chasing the same needs.' It provides a clear use context, though it does not name sibling alternatives or give exclusion criteria.

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