direct.hf.report_ads

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

Annotations already declare readOnlyHint=true and idempotentHint=true, but the description adds nothing beyond that: no indication of what the preset covers, what dimensions or date-range constraints apply, or pagination behavior. For a report tool with several near-identical siblings, this is a missed opportunity.

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 single phrase is brief but under-specified rather than concise; there is not enough content to be front-loaded or wasted. Brevity here reflects missing information, not efficiency.

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?

An output schema exists so return values need not be explained, but with 5 parameters at 40% coverage, no usage guidance, and an undefined 'preset', the definition is not complete enough for an agent to invoke it confidently against its many report siblings.

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?

Only 40% schema description coverage across 5 parameters, and the description contributes no parameter meaning at all. date_from/date_to/campaign_id are undocumented in both places, so the description fails to compensate for the coverage gap.

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?

It names the resource (Direct ads) and the operation class (report preset), which is more than a tautology. However, 'preset' is never defined, and siblings like direct.hf.report_performance, direct.hf.report_adgroups and direct.hf.report_keywords are not differentiated, so an agent cannot tell which report to pick.

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?

There is no when-to-use, no when-not-to-use, and no mention of the other report siblings. The agent must infer selection purely from the tool name.

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