Report how much the user has earned selling their tools. Use when they ask about sales, revenue, income, how much they made, how many calls were paid, or which tool sells best. Returns paid calls, gross revenue, commission and net revenue, broken down per tool. Requires the api_key from register_server.
| Name | Required | Description | Default |
|---|---|---|---|
| api_key | No | Your seller key. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and idempotentHint, so the description's job is lighter. It adds useful behavioral context by detailing the return fields (paid calls, gross revenue, commission, net revenue, broken down per tool) and the key requirement. It does not reveal potential rate limits or data freshness, but given annotation coverage, this is solid.
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?
Three crisp sentences: purpose, when-to-use, and output/prerequisite. Every sentence earns its place, and key info is front-loaded.
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 tool with one parameter, no output schema, and good annotations, the description covers the return structure and prerequisite sufficiently. The sibling-tool context and schema coverage complete the picture.
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 covers api_key 100% with a simple description. The description adds value by specifying the key's origin ('from register_server'), which is beyond the schema. This helps the agent know how to obtain the key.
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 ('Report') and clearly names the resource ('how much the user has earned selling their tools'). It immediately distinguishes this tool from siblings like set_tool_price or list_registered_servers by focusing on earnings, and even lists concrete use cases.
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?
It explicitly states when to use the tool: 'when they ask about sales, revenue, income, how much they made, how many calls were paid, or which tool sells best.' This provides clear guidance and implies such questions are not handled by other sibling tools. It also notes the prerequisite 'api_key from register_server.'
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.
Each tool has a clearly distinct purpose: earnings reporting, listing review, marketplace browsing, server registration, pricing changes, and ownership verification. There is no overlap between these operations, so an agent will not confuse them.
All tool names follow a consistent verb_noun pattern: get_earnings, get_my_listing, list_registered_servers, register_server, set_tool_price, verify_ownership. The style is uniform and predictable, making it easy to infer what each tool does.
Six tools is well-scoped for a payment and marketplace server. Each tool earns its place by covering a distinct aspect of the seller workflow without unnecessary bloat.
The tool surface covers the full lifecycle for sellers: registering a server, managing prices, viewing earnings, reviewing listing, and verifying ownership. There are no obvious dead ends or missing core operations for the stated purpose.