list_champions_of_reachRead the permanent paginated ranking of protocol-verified agent discoveries and structured outreach advertising placements.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | ||
| page_size | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful context beyond those annotations by noting the ranking is 'permanent,' 'protocol-verified,' and composed of structured outreach advertising placements, which helps the agent understand data stability and content provenance. No contradiction with annotations exists.
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 a single, front-loaded sentence with no filler. Every phrase contributes specific meaning: 'Read,' 'permanent,' 'paginated,' 'protocol-verified,' and the concrete content types all earn their place.
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 simple read-only pagination tool, the description is largely complete: annotations cover safety, the input schema covers page and page_size bounds, and an output schema exists. It could add a brief cross-reference to list_champions_of_genomics for alternative routing, but this is a minor gap given the clear resource naming.
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. The word 'paginated' signals that page and page_size govern pagination, which adds some meaning beyond the bare schema. However, it does not explain ordering, defaults, or paging behavior in detail; the schema's bounds and defaults carry most of the parameter semantics.
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 uses a specific verb ('Read') and names the exact resource: a permanent, paginated ranking of protocol-verified agent discoveries and structured outreach advertising placements. This clearly distinguishes the tool from its sibling list_champions_of_genomics by specifying the 'of reach' domain and the content type.
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 the tool is for reading a leaderboard-style ranking, which is sufficient for basic selection. However, it does not explicitly state when to prefer this over sibling tools such as list_champions_of_genomics or when not to use it, leaving some alternative-routing guidance to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Most tools are clearly separated by resource and action, but get_receipt and get_reach_receipt are easy to confuse because of their similar names and adjacent receipt concepts. The champions lists and relay tools are also related but their descriptions make the distinction clear enough.
Every tool follows a consistent verb_noun snake_case pattern (accept_, create_, get_, list_, register_, sponsor_, verify_). There is no mixing of conventions or vague generic verbs.
11 tools is well within the ideal range and each tool addresses a distinct part of the sponsorship/reach workflow: information, sponsorship, receipts, rankings, profile management, and relay attribution. No tool feels redundant.
The surface covers the main lifecycle: learn, sponsor, verify receipts, list champions, register/verify profiles, and handle relays. Minor gaps exist such as no tool to list relays or list receipts by account, but these can be worked around using known IDs.