Retrieve recent one-off supporters, newest first, with emails redacted unless include_emails is enabled for the account owner.
List recent one-off supporters, newest first, with emails redacted by default. Full emails belong to the account owner and should be handled accordingly when include_emails is true.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| since | No | ||
| max_pages | No | ||
| include_emails | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare the operation read-only, idempotent, and non-destructive. The description adds valuable behavioral detail beyond those hints: emails are redacted by default, full emails are sensitive account-owner data, and results are returned newest first. This gives the agent the privacy-relevant behavior it needs.
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?
Two sentences carry the essential scope, ordering, and privacy caveat with no filler. The main behavior is front-loaded and every phrase contributes information.
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 read-only annotations, self-explanatory pagination parameters, and sibling context, the description covers the key operational facts: what is listed, in what order, and what to do about emails. It does not spell out pagination behavior or the exact since filter, but those are reasonably inferable from the schema and parameter names.
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?
With 0% schema description coverage, description-level parameter guidance is required, and it only partially delivers. include_emails is well explained via the redaction and PII warning, and 'recent' loosely suggests the role of since, but limit, max_pages, and the exact filtering behavior of since are left to inference from their names and schema defaults.
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 specific action and resource ('List recent one-off supporters'), adds ordering ('newest first'), and notes default redaction, making the tool's purpose unmistakable. The qualifier 'one-off' distinguishes it from the sibling tools list_subscriptions and list_extra_purchases.
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 scope is clearly implied: it lists one-off supporters rather than subscriptions or extra purchases, so an agent can apply it when that resource is needed. It does not explicitly state 'use list_subscriptions for recurring supporters,' so it stops short of a full when/when-not rule, 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.