get_league_chat

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

Annotations already indicate readOnlyHint=true and openWorldHint=true description adds the caveat that 'History coverage and upstream order remain unverified.' This provides useful behavioral context beyond the annotations, warning the agent that results may be incomplete or not strictly ordered.

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 very concise, consisting of two short sentences. The core purpose is front-loadedlorized, and the caveat is valuable rather than filler. It could be improved by adding parameter semantics without bloating the text.

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 there is no output schema and no parameter descriptions, an agent likely cannot correctly invoke this tool without extra context. The description does not mention what a 'chat page' contains, how to paginate, or what 'before' expects. The caveat is interesting but not enough to make the tool usable.

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% for all three parameters (league_id, limit, before), and the description does not explain what each parameter does. 'Read a chat page' gives no clue about pagination semantics, the meaning of 'before,' or how limit applies. 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 states a clear verb and resource: 'Read a chat page.' It implies a read operation on a league chat, which distinguishes it from siblings like post_league_chat or search_league_chat. However, it does not explicitly mention 'league' or pagination in the purpose statement.

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 tool versus alternatives such as search_league_chat or post_league_chat. The description only says 'Read a chat page' with no exclusions or context for when the alternative tools should be chosen.

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