player_reward_delegation_history

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

With no annotations, the description carries full burden and delivers extensive disclosures: single logical GET request, no auto-pagination, local array limits of 100 rows and 256 KiB, truncation reporting, refusal of oversized records, and the limit/offset probe observation that an empty result does not prove end of history. This is unusually transparent.

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?

Every sentence contributes unique behavioral information, and the purpose is front-loaded. Minor grammatical issues ('Makes one logical GET request Does not auto-fetch') and a dense single paragraph slightly reduce readability.

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?

Despite the rich behavioral detail, there are still gaps: the description never explains the meaning of the eight parameters (beyond a generic filter-forwarding note), the exact return shape, or how token-based pagination works. For an 8-parameter tool with no output schema, this is incomplete.

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 coverage is 0%, so the description needed to compensate. It offers only general notes that required inputs reflect tool policy and that other filters are forwarded as supplied with no implied effectiveness. It does not explain what username, limit, offset, token, types, trx_ids, delegate_to_player, or delegate_to_players mean or how they combine.

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 'Read reward-delegation history for one player' provides a specific verb and resource, and the qualifier 'for one player' distinguishes it from global or multi-player endpoints. However, it does not explicitly contrast with the sibling player_reward_delegations, so the differentiation is implicit rather than explicit.

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 implies use for reading reward-delegation history for a single player, but gives no explicit when-to-use or when-not-to-use guidance and names no alternatives. The behavioral notes about pagination and filters are operational, not usage guidance.

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