create_analytics_report_request

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

No annotations are provided, so the description fully bears the burden. It discloses that the tool creates a request resource without modifying the app and explains the behavior of the two access types. It does not detail authorization requirements or rate limits, but the scope is clear for a non-destructive creation operation.

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 only two sentences, front-loading the purpose and return value, then efficiently explaining the access types and noting the non-modifying behavior. Every sentence contributes essential information without redundancy.

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 tool with 2 parameters (1 required) and no output schema, the description is complete: it covers the required parameter app_id, the optional access_type with its two options, the return value (reportRequestId) and a hint to pass it to list_analytics_reports. Nothing important is missing.

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 covers 100% of parameters, so baseline is 3. The description adds value by explaining the enum values (ONE_TIME_SNAPSHOT vs. ONGOING) beyond the schema's listing, and clarifies that app_id is the required identifier.

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 creates an analytics report request for an app, specifies it is the required first step to read App Store analytics, and returns a reportRequestId. It distinguishes the tool from siblings like list_analytics_reports by positioning it as the creation step.

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 explains the purpose of the tool as the first step to read analytics and differentiates between ONE_TIME_SNAPSHOT and ONGOING types. However, it does not explicitly state when not to use this tool (e.g., if a valid request already exists) or provide direct comparisons to sibling tools.

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