afl_broadcast_events

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

No annotations provided; the description reveals the return structure and that each entry is per match per channel, adding value beyond the schema. However, it omits details like pagination, authentication, or side effects.

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 brief with two sentences, no fluff, and the return format is shown. Could benefit from structured parameter info but remains efficient.

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 5 parameters, 0% schema coverage, no output schema, and no annotations, the description is insufficient. It does not explain how to use parameters or interpret results beyond the basic structure.

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 explain any of the 5 parameters (round, toDate, fromDate, pageSize, compseason). The description fails to compensate for the missing schema descriptions.

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 clearly states it provides a broadcast schedule with one entry per match per channel, distinguishing it from sibling tools like afl_broadcast_channels or afl_broadcast_match_events.

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?

No guidance on when to use this tool versus alternatives, nor any context on filtering or prerequisites. The description gives a high-level overview but lacks usage direction.

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