apple_get_finance_report

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

No annotations are provided, so the description carries the full burden. It never discloses that the full report is decompressed and written to a file at outputPath, that maxRows only truncates the inline response, or that overwrite controls file clobbering — all of which are actual side effects an agent must know about before calling.

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 front-loaded sentence with no filler. Appropriate in size, though it is arguably too terse for a 7-parameter tool that writes files.

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 7-parameter, no-annotation, no-output-schema tool that performs a file-write side effect, the description omits the essential facts (file output, truncation semantics, overwrite behavior, report type choice). It is not complete enough for correct invocation.

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 86%, so the schema already documents nearly every parameter, and the description adds no further semantics. The one enum (reportType: FINANCIAL vs FINANCE_DETAIL) is left entirely unexplained, and the behavior of the required regionCode/reportDate pair is only implied by the phrase 'earnings by region'.

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?

States a specific verb (download) and resource (monthly financial report, earnings by region) with a note on the return shape ('as rows'). It is distinguishable from sales/analytics sibling tools, though it never names the closest alternatives (apple_get_sales_report, apple_download_analytics_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?

No when-to-use guidance, no exclusions, and no pointer to which of the many Apple report/download siblings is the right one for a given need. The agent must infer selection purely from the name.

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