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

Annotations already flag destructiveHint=true, so the description does not need to restate that. It adds useful behavioral context beyond the schema: reports are emailed after each run, and create requires a re-runnable reference (connector:// or https://). There is no contradiction between the description and the 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 a single compact sentence with the main purpose front-loaded. It packs a lot of useful information without redundancy, though the parenthetical list is slightly dense.

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 the main actions and some create-specific details, but there is no output schema and no explanation of what 'list' returns or how schedule_id is obtained other than indirectly via the schema. For a multi-action tool with a nested object parameter, this leaves some operational ambiguity.

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?

With 67% schema description coverage, the schema handles some parameters, and the description adds meaning for action values, cadence (weekly/monthly), and dataset_ref (connector:// or https://). However, tool_name, schedule_id, and especially column_mapping receive no additional explanation in the description, leaving gaps for an agent to infer.

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 states the resource ('standing re-runs of analyses you own') and the specific verbs/actions ('create', 'list', 'cancel'). It clearly distinguishes this tool from one-off execution tools like run_analysis by emphasizing 'standing re-runs'.

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 clearly implies the tool is for recurring, scheduled re-runs and mentions weekly/monthly cadences, but it never explicitly contrasts with alternatives such as run_analysis or rerun_package, nor states when not to use this tool. The usage context is present but the guidance against/versus alternatives is left to inference.

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