Get Activity Feed

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals only the kinds of events included and says nothing about ordering, pagination, refresh behavior, permissions, or whether league_id null means a global feed; a short content list is insufficient for a feed with three parameters.

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 a single front-loaded sentence with no wasted words. It is concise, but it is undersized for a tool with three undocumented parameters and no annotations, so brevity comes at the cost of usefulness.

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 annotations, no output schema, and 0% parameter description coverage, the definition leaves an agent without the information needed to call the tool correctly. It should at least explain the league scope, pagination via start and max_items, and what the feed returns.

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 0% and the description does not mention any of the three parameters. It gives no meaning for start, league_id, or max_items, and does not explain the defaults or what a null league_id returns.

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 names a specific resource, 'League activity feed', and lists the event types it contains (transfers, market events, comments). However, it does not state the scope or filtering behavior, and it only weakly distinguishes itself from siblings like get_market or get_manager_transfers, which overlap in event content.

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?

There is no guidance on when to use this feed versus related sibling tools such as get_market, get_manager_transfers, or get_league_overview. The description gives implied usage only through its content list, with no exclusions or alternatives named.

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