ads_network_profile_publish

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. 'Publish' implies a mutation and public exposure, and the 'opt-in' plus data-exclusion language adds useful context, but the description omits permissions required, what the published profile exposes, whether publication is reversible, and which network receives it.

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 description is a single front-loaded sentence with no wasted words. It is appropriately compact, though its brevity contributes to the uncovered parameter and behavioral gaps.

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?

With six parameters, no annotations, no output schema, and zero schema description coverage, a one-sentence description is insufficient. An agent cannot determine what values to supply for required fields like kind and display_name, nor what happens on publication.

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?

The schema has six parameters and 0% description coverage. The description does not explain display_name, kind, id, regions, capabilities, or contact_relay at all, and the excluded 'credentials' and 'campaign data' are not even parameters in the schema.

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 gives a specific verb and resource: 'Publish an opt-in networking profile.' The added clause about excluding advertising credentials and raw campaign data clarifies scope, but it does not explicitly distinguish this from close siblings like ads_network_aggregate_publish or ads_network_placement_publish.

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 description states a data-exclusion constraint ('without advertising credentials or raw campaign data') but gives no guidance on when to use this tool versus ads_network_profile_list, ads_network_aggregate_publish, or ads_network_placement_publish. There are no prerequisites or selection conditions.

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