创建广告报告

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns a taskId and is asynchronous (requires polling). However, it does not mention authentication, rate limits, or side effects.

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 sentences, directly stating the purpose and the required follow-up action. No wasted words.

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?

With 6 required parameters, no output schema, and no annotations, the description is too brief. It does not explain enum values (e.g., adTypeCode, reportTypeCode) or the meaning of timeUnit, forcing the agent to rely on external knowledge.

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 coverage is 33% (only two date parameters have descriptions). The description does not explain any parameters, leaving the agent to infer meaning from enum names and property 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 uses specific verb '创建' (create) and resource '广告下载任务' (ad download task), and clarifies it is for daily reports (天维度报告). It distinguishes itself from siblings like sellfox_ad_report_query (polling) and sellfox_ad_report_download (downloading).

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 explicitly states the workflow: create task, get taskId, then poll with sellfox_ad_report_query. It does not provide when-not-to-use or alternatives, but the context implies this is for daily reports only.

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