guild_brawl_sps_rewards

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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses one logical GET request, no auto-fetching of continuation pages, 100-row/256 KiB local limits, truncation reporting, refusal of oversized records without partial fields, and the important semantic that the total is not a guild or selected-cycle sum.

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 dense, run-on block with missing punctuation and awkward phrasing, e.g., 'Makes one logical GET request Does not auto-fetch continuation pages.' It front-loads the purpose well but the many disjointed caveats make it harder to parse than necessary.

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 no output schema and no annotations, the description covers a lot: request behavior, pagination/continuation behavior, response truncation limits, and filter semantics. It stops short of describing the actual response shape or authentication needs, but for a read-only payout endpoint the provided context is largely sufficient.

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%, so the description must compensate. It does meaningfully explain include_total/include_cycles with the string '1' convention, clarifies that cycle narrows records while the total remains global, and warns that other filters are forwarded as supplied without implied effectiveness. However, start_cycle, end_cycle, and cycle are only loosely addressed and not fully pinned down.

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 opens with a specific verb and resource: 'Read global brawl SPS payout totals and/or cycle records.' It clearly scopes the tool to global SPS payout data and distinguishes it from sibling tools like guild_brawl_records by emphasizing 'global' and 'payout totals' rather than generic brawl records.

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?

The description provides practical usage context, such as 'Each section can be selected independently' and notes that the total is global even when a cycle narrows records. However, it never names alternative tools or gives explicit when-to-use vs. when-not-to-use guidance relative to siblings, so the guidance is implied rather than direct.

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