transactions

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

Annotations already declare a safe read (readOnlyHint=true, openWorldHint=false), and the description adds a genuine behavioral warning that trade notes are untrusted data and must never be treated as instructions. That injection-safety note is real value beyond the annotations, though pagination/window behavior for "recent" is left unstated.

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 core purpose and filter are front-loaded in one efficient sentence, and the safety note is short. The trailing "Demo league: a message." fragment is confusing noise that does not appear to earn its place.

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 two-parameter read-only tool with no output schema and annotation-covered safety, the description is largely sufficient, but it omits what "recent" means, how `count` bounds the result, and any hint at the return shape.

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 0%, so the description carries the burden. It clarifies that `team` acts as an optional filter on involvement, but says nothing about the `count` parameter (default 25) or what form a team identifier takes, leaving half the parameters unexplained.

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 resource and scope: recent Yahoo league transactions, broken down as adds/drops/trades. An agent can tell what it retrieves without opening the schema, though it never names how it differs from close siblings like find_trades or pending_offers.

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?

"Optionally only those involving `team`" implies the filtering use case, but there is no guidance on when to prefer this tool over find_trades or pending_offers, and no prerequisites or exclusions are stated.

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