player_lp_claim_history

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

With no annotations provided, the description carries the full burden and delivers rich behavioral details: it discloses pagination caveats (no working page-two cursor), explains that only one GET request is made without auto-fetching pages, warns that other filters are forwarded without effectiveness guarantees, and specifies local limits of 100 rows and 256 KiB with truncation reporting. It also notes oversized records are refused, which is valuable operational behavior.

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 moderately sized but dense with important details. It front-loads the core purpose and then adds caveats, but it could be structured better by separating behavioral constraints from parameter specifics. It avoids fluff, but some repetition of 'does not auto-fetch' and 'no working page-two cursor' could be streamlined.

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 thorough given the tool's complexity: it discloses limits, pagination behavior, request behavior, and parameter expectations. Without an output schema, it doesn't describe the return format, which is a minor gap, but the behavioral details are sufficient for an agent to call it safely. It's nearly complete, but a brief mention of response structure would fully match complexity.

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?

Although the input schema only provides parameter names with minimal types, the description adds semantic meaning: it identifies username as required, explains that limit and offset have specific behaviors (limit=1, offset=1), and clarifies that other filters are forwarded without implied effectiveness. Since schema coverage is 0%, the description compensates well by interpreting pagination parameters.

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 clearly identifies the tool's purpose: reading liquidity-provider claim history for a single player. It specifies the verb 'Read', the resource 'liquidity-provider claim history', and the scope 'for one player', which distinguishes it from broader history tools among siblings.

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 contextual usage hints: it notes that limit=1 produced one row, limit=2 with offset=1 repeated rows, and declares no working page-two cursor, guiding agents on pagination behavior. However, it lacks explicit statements of when to use this tool versus alternatives, though the 'for one player' scope implies alternatives.

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