ads_network_aggregate_publish

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

With no annotations, the description carries the full burden, and it only discloses one trait: the privacy guarantee that the relay never receives raw local events. It says nothing about whether this mutates remote state, how duplicates are handled (despite a required dedupe_key), permission requirements, rate limits, or what is returned.

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 short sentences with no filler, and the core action is front-loaded before the privacy note. Brevity here is efficient, though it borders on under-specification for an 11-parameter mutation.

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 11 undocumented parameters, no annotations, and no output schema, the description is far too thin. It conveys the intent and the privacy model but leaves the agent unable to construct a correct call or anticipate the response.

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?

There are 11 parameters with 0% schema description coverage, including five required identifiers (dedupe_key, node_ref, scope_ref, period_from, period_to). The description explains none of them, so an agent cannot know what node_ref versus scope_ref refers to, what unit the period strings use, or how dedupe_key affects repeated calls.

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 and resource: an opt-in publish of aggregated campaign metrics, which is a clear action. It does not differentiate itself from adjacent siblings such as ads_network_conversion_report or ads_network_placement_publish, and the actual destination ('the relay') is only implicit.

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?

The only usage signal is the word 'Opt-in', which hints at a consent prerequisite but never states when to call this instead of ads_network_platform_report or ads_network_conversion_report. No exclusions, preconditions, or ordering guidance are given.

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