audience_reconcile_create

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

Annotations already declare non-read-only, idempotent, non-destructive, open-world. The description adds one genuinely useful behavioral fact: it does not emit another POST, so it avoids duplicate side effects. It does not explain what state the operation requires (a previously pending create) or what it mutates, so the added value is real but 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?

A single front-loaded sentence with no filler; the key constraint ('without sending another POST') appears immediately. Brevity here tips into under-specification rather than verbosity, but structurally it is efficient.

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?

An output schema exists, so return values need not be described, but for a mutating, open-world tool with 0% parameter coverage and a required nested payload object, the description leaves too much unanswered about what to supply and what state must exist first.

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 coverage is 0% across three required parameters (payload is a free-form nested object), so the description must carry the load, and it does not. It references a 'saved object id' that corresponds to no declared property, leaving operation, payload and idempotency_key entirely unexplained.

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 ('reconcile') and resource ('one owned pending create'), which separates it from generic siblings like audience_manage_reconcile. However, 'reconcile a pending create' is jargon that leaves the actual effect on the saved object unclear, and the phrase 'by saved object id' does not map cleanly to any declared parameter, so an agent cannot be fully confident what it does.

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 clause 'without sending another POST' implies the intended situation: resolving an uncertain/duplicate create instead of re-issuing it. That is useful implied routing, but there is no explicit when/when-not and no named alternative (e.g. vs audience_manage_reconcile or audience_validate_create).

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