get_good_rulesRead the exact financial, outreach, advertising, representation, privacy, and scientific-independence rules. No payment or write is initiated.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is structurally known. The description reinforces this with 'No payment or write is initiated' and adds useful content scope, but it does not disclose additional behavioral traits such as permission requirements, freshness guarantees, or rate 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 two short sentences with the action and resource front-loaded, followed by a concise safety clarification. Every sentence earns its place and there is no filler.
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 parameterless, read-only tool with strong annotations and an output schema, the description is complete enough. It states what rules are covered and that invocation has no side effects; no necessary operational detail is missing.
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?
There are zero parameters, so the input schema is fully covered and the description has no parameter-level burden. The baseline for a parameterless tool is 4.
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 the specific verb 'Read' and names the resource clearly: 'the exact financial, outreach, advertising, representation, privacy, and scientific-independence rules.' This distinguishes the tool from sibling getters like get_campaign and get_receipt, which concern different resources.
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 used when the agent needs the governing rules and assures the call is side-effect-free, but it does not explicitly state when to prefer this tool over alternatives or when not to use it. For a unique zero-parameter getter, this is acceptable but still only implicit.
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.