analytics_report_requests__create

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

The description adds behavioral detail beyond the annotations (which only indicate non-read-only, non-idempotent, non-destructive) by stating that nothing is downloadable immediately and that a fresh request has no instances for a day or more. It also explains the behavior of the two access types.

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 three sentences, each carrying essential information: the operation, the access type meanings, and the availability delay. It is front-loaded with the core purpose and contains no redundant text.

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 create operation with a nested body schema and no output schema, the description covers key aspects: what it does, the choice of access types, and the expected delay. It does not describe the response shape, but the absence of an output schema makes this less critical.

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 schema provides only a generic description for the body parameter, but the description adds meaning to the accessType enum by explaining what ONE_TIME_SNAPSHOT and ONGOING mean. This goes beyond the raw enum values listed in the schema.

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 ('Ask Apple to start producing analytics for an app') and the specific resource (analytics report request), distinguishing it from sibling tools like analytics_report_requests__get and __delete. The endpoint is also included, reinforcing the operation.

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 provides context for selecting access types (ONE_TIME_SNAPSHOT vs ONGOING) and explains the delay before data is available. It does not explicitly name alternative tools, but the action verb 'start producing' and the explanation of access types imply when this create operation is appropriate.

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