get_gmvmax_reports_tool

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

No annotations provided; description does not disclose behavioral traits (e.g., read-only, rate limits, auth requirements). Only mentions API endpoint.

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?

Relatively concise, with line breaks separating information. No wasted sentences, though could benefit from structured formatting (e.g., bullet points).

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?

Covers essential aspects: required store_ids, available metrics/dimensions, filtering format. Missing date format, pagination, and confirmation that some metrics may require specific dimensions. Output schema exists but not shown.

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%; description explains store_ids, metrics list, dimensions list, and filtering structure. However, omits descriptions for page, page_size, start_date, end_date, advertiser_id.

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?

Clear verb 'Get' and resource 'GMV Max performance reports' with API endpoint. Lists metrics and dimensions. However, does not differentiate from sibling tools like get_gmvmax_range_report_tool or get_gmvmax_report_aligned_tool.

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?

Provides guidance on required store_ids and filtering with campaign_ids/item_group_ids when using item_id dimension. Lacks explicit when-to-use vs alternatives or exclusions.

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