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 it delivers rich behavioral disclosure: it reports observed pagination behavior, states that it makes one logical GET request, does not auto-fetch continuation pages, and explains local truncation at 100 rows/256 KiB with truncation reported in text and metadata, plus refusal of oversized records without partial fields. This is far beyond what a typical description provides and directly informs an agent about side effects and limits.

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 dense but every sentence earns its place: purpose, pagination caveat, request behavior, filter caveat, and truncation policy. It is front-loaded with the core purpose. It could be slightly more structured, but it is not bloated.

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?

For a read-only history tool with no output schema and no annotations, the description covers the essential operational context: pagination limitations, request count, truncation, and filter reliability. It doesn't describe the return shape, but without an output schema that would be a larger omission; still, the description is unusually complete for this tool family.

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 clarify that username is a required input reflecting tool policy and upstream requirements, and it explains that other declared filters are forwarded as supplied without implied effectiveness. It doesn't define each parameter's format or meaning, but it gives the most important semantic guidance: which inputs are meaningful and which are not guaranteed to filter. Given the 0% coverage, this is strong compensation, though not exhaustive.

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 clear verb and resource: 'Read liquidity-provider claim history for one player.' This distinguishes it from the many player_* siblings by specifying the claim-history resource and the single-player scope. It doesn't explicitly name a sibling alternative, but the scope is specific enough to orient an agent.

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 gives concrete usage context: it notes that limit=1 returned one leading row, limit=2 with offset=1 repeated rows, and that no working page-two cursor is established. This tells an agent that pagination is unreliable and that they should not rely on offset for multi-page reads. It also states that other declared filters are forwarded as supplied but their effectiveness is not implied, which is honest guidance about when not to assume filtering works. It doesn't explicitly name an alternative tool, but the context is clear.

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