Petal Ads report

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

Annotations indicate readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description consistently describes a query operation (query, returns). It adds context about the API and metrics returned, which is useful beyond the annotations.

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 front-load the purpose and capabilities. No redundant information. Every word adds value.

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?

Given 14 parameters with full schema descriptions and annotations indicating read-only behavior, the description covers the tool's purpose and output. It could mention pagination or rate limits, but the parameters (page, page_size) address pagination implicitly. Minor gap for 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 coverage is 100% with all parameters described. The description provides a high-level overview but does not add new meaning beyond the schema. Baseline 3 is appropriate as the schema carries the detail.

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 queries the Huawei Petal Ads reporting API with control over grouping, filtering, ordering, and pagination. It specifies the resource (reports), action (query), and expected return values (monetization data including earnings, impressions, clicks, rates). This distinguishes it from siblings like petal_apps_performance and petal_revenue_summary.

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 such as petal_apps_performance or petal_revenue_summary. The description implies full control but does not explicitly state contexts where this tool is preferred or when not to use it.

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