Download a sales/financial 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 discloses that the tool decodes the report and returns parsed rows, including the truncation to 500 rows. However, it does not mention authentication requirements, error conditions, or whether the operation is read-only. This is adequate but not comprehensive.

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 with no wasted words. It front-loads the core action and return behavior, and is well-structured for quick parsing.

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, the description explains the return value as parsed rows and notes truncation. It covers the main behavior and source. It lacks explicit mention of prerequisites or error handling, but for a download tool this is fairly complete. Slight deduction for not specifying authentication or failure cases.

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 description coverage is 100%, so all parameters are already documented in the schema. The description adds little beyond mentioning that the report is TSV and that output is truncated, which does not clarify parameter semantics. The baseline of 3 applies since the schema fully handles parameter documentation.

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 action (Download and decode), the specific resource (sales or subscription report from App Store Connect), and the return format (parsed rows truncated to 500). This distinguishes it from sibling tools that focus on apps, builds, or Game Center features.

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 implies usage for downloading sales or subscription reports, but does not explicitly state when to use this tool versus alternatives. It provides no exclusions or alternative tool names. The intended use is implied by the tool's purpose, but no direct guidance is given.

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