get_ads_report_aligned_tool

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

Description discloses that it fetches hourly data and re-aggregates, and lists returned fields. However, with no annotations, it lacks information on destructive behavior, rate limits, or authentication requirements. It does not contradict annotations since none exist.

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?

Three sentences: purpose, process, returned metrics. Compact and front-loaded. No redundant information.

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?

For a tool with 4 parameters and no param descriptions, the description covers the core purpose and output but omits parameter details and usage context. Output schema is present, so return values are documented elsewhere. Adequate but not comprehensive.

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 has 0% parameter description coverage, so description must compensate. It mentions the shop_tz alignment and date, but does not explain advertiser_id, metrics array, or default values. Only minimal parameter context is provided.

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?

Description clearly states the tool gets an ads report aligned to shop timezone, specifying manual bid, hourly data, and returned metrics. It distinguishes from siblings by highlighting timezone alignment and aggregation.

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?

Description implies usage for timezone-aligned reports but does not explicitly state when to use or when to avoid, nor does it mention alternatives like get_ads_range_report_tool. Guidance is inferred rather than explicit.

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