get_affiliate_campaign_usage

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

States API call (GET) implying read-only behavior, but does not explicitly declare non-destructive nature or other traits like rate limits. Without annotations, description partially compensates.

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?

Well-structured with sections (purpose, usage, API, return), but slightly verbose. Each sentence adds value; no wasted text.

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 no output schema, description provides return structure (dict with fields and units TWD). Covers all needed info for agent to invoke and parse results.

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?

Adds crucial info beyond schema: campaign_id is from list_affiliate_campaigns' id field, guiding the agent to chain calls correctly.

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?

Clearly states '取得...訂單使用統計' (get order usage statistics) with detailed description of returned data (orders, revenue, commission), distinguishing it from sibling get_affiliate_campaign_detail.

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?

Explicitly describes when to use: '分析特定聯盟行銷活動的訂單數與銷售額，評估推廣效果' (analyze orders and revenue for campaign performance). No explicit when-not-to-use but context is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.