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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, but the description adds context annotations cannot: the overwrite "cannot be undone from NewsJack," the write uses a server-level TAP_API_KEY rather than a per-user login, it fails when that key is missing or TAP refuses, and it requires the generate:posts scope without consuming a NewsJack allowance. It even names the return payload. The one gap is the absence of any partial-failure guidance (e.g., whether a campaign is created before the goal write fails).

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?

Purpose and the when-to-call gate are front-loaded, and nearly every sentence carries distinct information (auth model, mutation semantics, return shape, scope, non-idempotency). It is delivered as a single dense paragraph with no structural breaks, which makes the mode-switching rules between content_id/content and campaign_id/new-draft harder to scan than they need to be.

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?

This is an open-world, destructive, non-idempotent write with no output schema, and the description covers everything an agent needs: preconditions, auth model, branch behavior, irreversibility, failure condition, and the shape of the returned receipt. Nothing material is left to the schema or annotations to guess at.

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 100%, so baseline would be 3, but the description adds a constraint the schema cannot express: with zero required parameters, at least one of content_id or content must be supplied. It also restates the precedence rule that content_id overrides content and platform and describes what campaign_id does to the target's goal field.

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?

"Send one Jack to a Total Audio Promo (TAP) campaign, creating a new draft campaign or writing into an existing one" gives a specific verb, resource, and the two operating modes. No sibling tool touches TAP, and the description makes that external boundary explicit ("TAP is a separate product"), so an agent can select it unambiguously.

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?

It states an explicit gate: "only call this when the person has asked for the Jack in TAP," which rules out speculative or default use. It also explains the two input modes (content_id versus content) and the two output modes (campaign_id versus a new draft), including the warning that omitting campaign_id on a repeat call creates another campaign.

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