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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description adds nothing beyond that – no information about ordering behavior beyond the schema's 'hot' default, no pagination, no note on what a replay record contains or whether results vary over time. The one sentence only restates the resource.

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?

A single front-loaded sentence with no wasted words. It is efficient but verges on under-specification, since nothing beyond the core noun phrase is conveyed.

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?

This is an open-world listing tool with four optional filters and no output schema, yet the description says nothing about what a replay object contains, how results are ordered across the sort options, or what an empty result means. For a tool whose return shape is undocumented elsewhere, more guidance is warranted.

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 100% with all four optional filters (tag, coin, sort, limit) documented in the schema including the enum and 1–10 bound. The description adds no extra meaning about how filters combine or what happens when none are supplied, so the baseline of 3 applies.

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 gives a specific verb and resource ('List live stream replays') plus the source ('Gate Square'), so an agent knows exactly what entity is being retrieved. It stops short of distinguishing this from the nearest sibling, cex_square_list_square_ai_search, which retrieves a different kind of Square 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 statement of when to use this tool versus alternatives, no prerequisites, and no exclusions. The agent must infer from the name alone that this is the tool for replay listings rather than search results.

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