get_creative_report_tool

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

With no annotations, the description carries full burden. It provides only the basic function and default report type. No disclosure of side effects, authentication requirements, rate limits, or output behavior. The output schema exists but the description adds no context about it.

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 very short, but lacks structure. It combines a brief purpose statement with a parameter note. While concise, it does not use space efficiently to convey critical 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?

Despite having an output schema, the description omits details about date formats, pagination behavior, filtering capabilities, and return values. For a tool with 7 parameters and 3 required, this is inadequate.

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 only mentions report_type and its default. It fails to explain the purpose or constraints of parameters like page, page_size, filtering, or the required advertiser_id, start_date, and end_date. This is insufficient for correct usage.

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 gets a creative-level performance report focused on video insights, engagement, and play metrics. It mentions the default report_type, which helps specify the scope. However, it does not differentiate from many sibling report tools like get_reports_tool or get_ads_range_report_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?

No guidance on when to use this tool versus alternatives. The description does not mention any prerequisites, conditions, or exclusions. An agent would need to infer usage from the name alone.

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