create_report_request

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

Annotations already indicate write, non-idempotent, non-destructive behavior. The description adds useful context: it is the only write operation, and it explains the timing difference between ONGOING (data starts next day) and ONE_TIME_SNAPSHOT (returns historical data). It does not elaborate on repeated calls, but does not contradict annotations.

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?

Three sentences, no redundancy. The purpose is front-loaded, followed by critical context (only write op, requirement), then mode-specific behavior. Every sentence earns its place.

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?

The description covers purpose, necessity, and mode behavior. An output schema exists, so return format is covered. The only minor gap is the lack of guidance on repeated calls, but annotations signal non-idempotency, so this is not 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?

Schema coverage is 100%, so parameters are documented. The description adds value by explaining the behavioral difference between the two access_type values, which goes beyond the schema's terse description. This helps an agent choose the right mode for the desired outcome.

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 ('enable analytics reports') and the resource ('report request'), and distinguishes it from all sibling tools by noting it is the only write operation. It also explains the requirement per app, making its purpose unmistakable.

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?

It explicitly identifies this as the required write operation for enabling reports, and contrasts it with the listing tools in the sibling set. It does not explicitly say 'use this instead of X', but the context is clear. It could mention what happens if called multiple times, but the necessity is well-stated.

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