Request Analytics Reports

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

Annotations declare idempotentHint=true and readOnlyHint=false. The description reinforces idempotency by stating it reuses an existing request if present, and adds behavioral details like the note about 48-hour generation time and the return object structure, providing useful context beyond 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?

The description is extremely concise: a single-purpose sentence, a usage ordering instruction, and a structured args/returns section. Every sentence is necessary and adds value 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?

Given the tool's simplicity (1 param, no output schema), the description fully covers the behavior, return values, and usage context. It explains the idempotent behavior, the created flag, and the 48-hour latency, making it complete for an agent.

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 description of appId matching the tool's param docs. The description repeats the param info but adds no new semantic meaning beyond the schema's description. The return object is described in detail, but parameter semantics add minimal value.

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 ensures an ONGOING analytics report request exists, using the verb 'ensure' and specifying the resource. It distinguishes itself from siblings by noting to call this before asc_list_analytics_reports, which lists rather than creates/reuses requests.

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?

Explicitly states when to use: 'Ensure an ongoing analytics report request exists' and 'Call this first, before asc_list_analytics_reports.' While it doesn't list alternatives for other use cases (e.g., one-time reports), the guidance is clear and actionable.

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