analytics_report_requests__create

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

Annotations are present with readOnlyHint=false, idempotentHint=false, destructiveHint=false, indicating this is a non-idempotent write operation. The description adds no behavioral context beyond 'Create', but it does not contradict annotations. With annotations providing baseline, a score of 3 is appropriate.

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 extremely concise with a single sentence that includes the purpose and HTTP endpoint. No unnecessary words or clutter, making it efficient for an agent to parse quickly.

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?

Despite no output schema, the description fails to mention what the response returns (e.g., the created report request ID or status). For a creation tool, this is a significant gap. Annotations are present but do not fill this need. The description is incomplete for guiding agent expectations.

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 100%, with the body parameter already described as 'JSON:API request body (Apple schema: AnalyticsReportRequestCreateRequest)'. The tool description does not add any further parameter meaning beyond what the schema provides, so a baseline score of 3 is given.

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 verb 'Create' and the resource 'analytics report request', which is distinct from sibling tools like analytics_report_requests__delete and analytics_report_requests__get. The HTTP method and path are also provided, making the purpose unambiguous.

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 no guidance on when to use this tool versus alternatives, such as when to create versus request existing reports. No prerequisites or context for usage are given, leaving the agent without decision-making support.

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