ads_network_placement_publish

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

With no annotations, the description carries the full disclosure burden. 'Provider credentials stay local' is a useful security note, but it doesn't say whether publishing is a mutation with side effects, whether the placement enters a review state, whether calls are idempotent, or what permissions are required. For an 11-parameter mutation this is thin.

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, front-loaded with the action and with zero filler. The brevity is structurally sound, though it reflects under-specification rather than economy of expression.

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?

A mutation tool with 11 parameters, 4 required, nested objects, zero schema descriptions, no annotations, and no output schema demands far more. Nothing tells the agent what a successful publish returns, how errors surface, or how the nested audience/pricing structures must be shaped.

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 0% across 11 parameters including nested objects (audience, pricing) and a suspicious $ref from pricing to audience. The description gives no hint about required fields (publisher_ref, name, channel_type, pricing) or what the nested audience object should contain, so it does nothing 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 (publish) and a specific resource (an opt-in advertising placement offer), which is more than a restated name. It does not, however, distinguish itself from close siblings like ads_network_profile_publish or ads_network_aggregate_publish, so an agent cannot tell which publish variant applies without opening schemas.

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?

'Opt-in' hints at a consent prerequisite but the description never says when to choose this over the sibling publish tools or what conditions must hold before calling. No exclusions, prerequisites, or alternatives are given.

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