delegations_incoming

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

With no annotations provided, the description carries the full behavioral burden, and it excels. It discloses paging behavior (one bounded GET, no auto-paging), data preservation rules (amount strings, rental fields, nullable dates), absence of inference, measurement caveats (sort effectiveness unmeasured), local limits (100 rows, 256 KiB), truncation reporting, and refusal of oversized records without partial fields. This is exemplary transparency.

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 verbose and dense, with many hedging caveats like 'Paging is declared but not independently demonstrated' and 'Sort effectiveness is unmeasured'. While informative, it lacks conciseness; the key purpose is front-loaded, but the subsequent sentences are numerous and could be tightened. It reads more like a QA report than a tool description, reducing scannability.

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 the tool has 5 parameters, no output schema, and no annotations, the description covers a wide range of operational concerns: paging behavior, size limits, truncation, refusal policy, filter forwarding, and data preservation. It is nearly complete, though it does not describe the response format in any detail (e.g., field names, structure) or the meaning of 'SPSP' for domain novices. Still, it addresses most practical invocation concerns comprehensively.

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 for parameter meaning. It only states that required inputs reflect tool policy and that filters are forwarded as supplied, but it does not explain the semantic role of sort, order, offset, or even the player/limit parameters beyond the schema's basic types. The note about size limits relates to limit but not its meaning or defaults. The description adds minimal semantic value beyond the schema, leaving agents to guess at valid sort/order values or offset behavior.

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 incoming SPSP delegation records', and immediately clarifies that each returned player is a delegator to the explicitly requested player. This distinguishes it from sibling tools like delegations_outgoing and delegation_to_target, which handle the opposite direction or specific targets. The purpose is unambiguous.

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 offers some context about what the tool does not do (no currency conversion, no card-delegation inference) and hints at relationships with outgoing/pairwise reads, but it never explicitly states when to use this tool versus alternatives. It mentions 'Required inputs reflect tool policy' but gives no concrete selection criteria. There is no direct comparison to sibling tools or conditions for choosing this endpoint, so usage guidance is partial.

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