player_reward_delegation_history

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

With no annotations, the description fully carries the behavioral burden and does so well. It discloses pagination quirks, the absence of auto-fetch continuation pages, local response limits (100 rows, 256 KiB), truncation reporting, and refusal of oversized records. This is far beyond the minimal 'read history' statement.

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 longer than average but every sentence adds important caveats about pagination, truncation, or filter behavior. It front-loads the purpose and keeps the most critical operational facts visible, though the probe anecdote could be tightened.

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?

The description is unusually rich in behavioral detail, especially given the lack of annotations and output schema. However, it still leaves a gap around individual parameter meaning and response structure, which matters for an 8-parameter tool with 0% schema description coverage.

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%, yet the description does not meaningfully explain most of the eight parameters. It mentions limit and offset in a probe scenario, but does not define their expected values or semantics. The general statement that filters are 'forwarded as supplied' warns about effectiveness but does not clarify what types, trx_ids, or delegate_to_player mean.

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 opening sentence states a specific verb ('Read') and resource ('reward-delegation history') scoped to one player. This clearly distinguishes it from the sibling player_reward_delegations, which likely covers current delegations rather than historical 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 never explicitly tells an agent when to choose this tool over alternatives such as player_reward_delegations, delegations_outgoing, or player_balances_history. It provides behavioral caveats but no decision guidance about which sibling covers current vs. historical data.

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