下载广告报告

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

No annotations are provided, and the description only mentions 'download and parse' without disclosing behavioral traits like whether it is read-only, authentication requirements, rate limits, or side effects. Given the absence of annotations, the description fails to carry the full burden of transparency.

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 concise with one sentence that presents the action and input source upfront. It avoids unnecessary words, but could be slightly expanded for clarity without losing conciseness.

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 single parameter and no output schema, the description provides the essential input source and purpose. However, it lacks details about output format, error handling, or any constraints, leaving some gaps for an agent to fully understand the tool's usage.

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?

The input schema has one parameter 'url' with 0% description coverage, but the description adds context that the URL should come from sellfox_ad_report_query. This adds meaning beyond the schema, but does not specify format or constraints, resulting in moderate semantic addition.

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 clearly states the tool downloads and parses advertising report files, specifying the input is the download link from the sibling tool sellfox_ad_report_query. This differentiates it from other sibling tools that perform different report operations.

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 advises using the download link from sellfox_ad_report_query, providing clear context for when to use this tool. While it does not mention alternatives or when not to use it, the guidance is sufficient for the intended workflow.

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