cloud_affiliate_statsRead affiliate stats, payout availability and recent commissions to track earnings and payouts. Filter by status or limit results for reporting.
Đọc thống kê, số dư có thể nhận và các hoa hồng gần nhất. / Read affiliate stats, payout availability and recent commissions.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | ||
| status | No |
Changes observed during successful MCP inspections.
v0.11.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful return-content context, but does not disclose pagination behavior, filtering behavior, or permission requirements beyond what annotations provide.
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 compact sentence with no wasted clauses, front-loading the core action and returned data. The bilingual duplication is acceptable and does not meaningfully reduce clarity.
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 stats tool with rich annotations, the description is adequate about the general purpose. However, it is incomplete for invocation because neither optional parameter is documented or explained, and there is no output schema to compensate.
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%, and there are two parameters (limit and status). The description mentions recent commissions and payout availability, but never explains what limit controls or how the status enum filters results, leaving the agent to infer parameter behavior from names alone.
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 states a specific verb and resource: read affiliate stats. It also lists the key returned content categories (payout availability, recent commissions), which distinguishes this tool from sibling affiliate actions such as link creation and claim/payout execution.
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?
Usage is implied by the read-oriented purpose, but the description gives no explicit when-to-use guidance, prerequisites, or comparison against alternatives like cloud_affiliate_claim. An agent can reasonably infer this is the stats-reading tool, but routing guidance is minimal.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.