apple_download_analytics_report

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

With no annotations, the description carries the full burden. It discloses the segment download + decompress + merge behavior, which is useful, but never states that the tool WRITES A FILE to disk, what happens on overwrite refusal, whether downloading is long-running or rate-limited, or what it returns. The file-writing side effect is only visible in the schema.

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?

A single tight sentence with the core action front-loaded and zero filler. It is efficient, though it stops short of including the file-output detail that would make it self-sufficient.

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 4-parameter tool with no annotations and no output schema, the schema covers two of the parameters reasonably well. What is missing is the prerequisite state of the report instance and the on-disk side effect / error behavior when overwrite is false, which an agent needs before calling it.

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 75%, with maxRows and outputPath (and their interplay, full report to file vs. rows in response) documented in the schema, so baseline 3 applies. The description adds nothing about parameters, and instanceId is undocumented in both the schema and the description.

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 ('Download') with a clear resource ('every segment of an analytics report instance') and adds what it does with them ('decompress and merge them into rows'). It implicitly distinguishes itself from the sibling listing tools (apple_list_analytics_report_segments, apple_list_analytics_report_instances) that only enumerate, but it never names a sibling or explicitly contrasts with apple_get_sales_report / apple_get_finance_report.

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?

There is no when-to-use guidance, no stated prerequisites (e.g. the report instance must be completed/ready before downloading), and no mention of alternatives. The agent must infer that this follows the list-analytics-report-instances flow.

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