run_report

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, but it only offers a generic action. It doesn't state whether running a report is synchronous, requires specific permissions, has side effects, or what form the results take.

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, front-loaded sentence that efficiently states the tool's action. However, it misses the opportunity to include useful behavioral context without adding significant length.

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?

With no output schema, the description needed to clarify what 'results' means (raw rows, a URL, status message), but it only says 'get its results.' Combined with the lack of usage guidance and behavioral transparency, the description is not sufficient for confident invocation and interpretation.

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 description coverage is 100% since the only parameter, `id`, includes a helpful example format ('gid://shopify/Report/123456789'). The tool description itself adds no parameter-level meaning, so the baseline 3 applies.

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 'Run a report and get its results' uses a clear verb+resource construction and avoids being a tautology. However, it doesn't distinguish this tool from closely related siblings like get_report or get_analytics_report, and doesn't specify the scope of 'results'.

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 vs. alternatives such as get_report, get_analytics_report, or run_shopifyql_query. There are no prerequisites, exclusions, or contextual cues to help an agent choose correctly.

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