get_gmvmax_report_aligned_tool

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

No annotations are provided, so the description carries the burden. It discloses timezone realignment and lists returned metrics (cost, gross_revenue, orders, ROI, hours), but lacks details on idempotency, side effects, or authentication requirements.

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?

Two sentences, no filler, front-loaded with purpose. Every word contributes: 'Get', 'GMVMAX report', 'aligned to shop timezone', description of re-aggregation, and list of returned fields.

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 an output schema present, the description need not detail return values, but it omits how the date parameter is interpreted (single day?), error conditions, and behavior for missing data. The tool's complexity (timezone logic) warrants more completeness.

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 0%, but the description adds minimal parameter meaning. It mentions 'hourly data' implying time granularity, but does not explain date format, shop_tz default, store_ids, or advertiser_id. The metrics parameter is hinted at but not detailed.

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 retrieves a GMVMAX report aligned to shop timezone, distinguishing it from siblings like get_gmvmax_range_report_tool and get_gmvmax_reports_tool which may not realign timezones. It specifies the verb 'Get', the resource 'GMVMAX report', and the unique behavior 'aligned to shop timezone'.

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 implies usage when a daily report aligned to shop timezone is needed, but it does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusions or prerequisites are mentioned.

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