direct.hf.unarchive_ads

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses almost nothing: no indication that this is a state-changing mutation, no explanation of how apply vs dry_run interact (a safety-relevant behavior for an unarchive), no permission or auth requirements, and no note on partial failure when a list of ad_ids is passed. The only hint is "Human-friendly," implying a higher-level wrapper.

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?

It is a single short sentence and therefore not bloated, but "Human-friendly:" is filler that does not earn its place, and the extreme brevity is under-specification rather than true conciseness given the tool's complexity.

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 seven-parameter mutation tool with zero annotations, no output schema, and 29% schema coverage, a four-word description is wholly inadequate. An agent cannot determine required inputs, safe invocation order, or the effect of the operation from this definition.

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 only 29% (just account_id and direct_client_login), so the description must compensate for the other five parameters and does not. In particular apply, dry_run, and the choice between ad_ids vs campaign_id/campaign_name are entirely undocumented, leaving the agent to guess the targeting and preview semantics.

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?

"Unarchive ads" is a specific verb+resource and is unambiguous on its own, but it essentially restates the tool name (direct.hf.unarchive_ads) and the "Human-friendly:" prefix adds only a vague hint that this is a simplified wrapper rather than a raw call. Nothing distinguishes it from siblings like direct.hf.archive_ads, direct.hf.unarchive_campaigns, or direct.hf.moderate_ads.

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 guidance on when to use this versus the inverse (direct.hf.archive_ads), the campaign-level variant (direct.hf.unarchive_campaigns), or direct.raw_call. No prerequisites, no mention of whether campaign/ad ids or names are required. The agent must infer everything.

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