direct.hf.set_campaign_tracking_params

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

With no annotations, the description carries the full behavioral burden. '(best effort)' does disclose that the operation is not guaranteed to fully succeed, which is real value. But it says nothing about the behaviorally critical apply/dry_run parameters, what gets overwritten, permission requirements, or response shape for a 7-parameter mutation tool.

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?

A single short sentence with no wasted words, and the operation is front-loaded. Given the 7-parameter surface and zero annotation support, however, it is arguably under-specified rather than concisely complete.

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 mutation tool with 7 parameters, no required-parameter guidance, no annotations, and no output schema, a one-line description is inadequate. An agent cannot determine the roles of apply/dry_run or which identifier (campaign_id vs campaign_name) to supply.

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% (2 of 7 params: account_id and direct_client_login). The description mentions 'TrackingParams' loosely mapping to tracking_params, but apply, dry_run, campaign_id, and campaign_name are undocumented in both schema and description. Far too thin 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?

States a specific verb (set) and resource (TrackingParams for a campaign), so an agent knows what the tool does. However, it does not differentiate itself from the sibling direct.hf.set_adgroup_tracking_params, and the 'Human-friendly' prefix adds no discriminating value.

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 guidance, no mention of prerequisites, and no routing to alternatives. The '(best effort)' parenthetical hints at expected behavior but provides no selection criteria between this tool, the adgroup variant, or direct.hf.set_campaign_utm_template.

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