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

Annotations already flag the write, non-idempotent, non-destructive profile, and the description adds meaningful behavior: default status is active, incoming postbacks without a currency are converted from payout_currency, and dest_kind local means the tracker hosts the page. It does not mention duplicate-name handling, permission requirements, or error behavior, so it stops short of a 5.

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 dense paragraph that front-loads the required-field and default information, then explains macros and the local-offer case. Every sentence carries content, though the run-together style makes the local-offer clause easy to miss.

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 23-parameter creation tool with no output schema, the description covers the common path well but omits what is returned on success (presumably an offer id), and leaves a large block of parameters unexplained. Annotations carry the safety profile, so the gap is moderate rather than critical.

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?

With 23 parameters and 57% schema coverage, the description explains several important ones (payout_type, status default, payout_currency, URL macros, dest_kind local plus ZIP). But much of this restates schema text, and roughly a dozen parameters (caps, tags, group_id, aff_network_id, redirect_type, push/heatmap options) get no mention in either prose or 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 opens with a specific verb and resource ('Create an offer.') and immediately scopes what is required versus defaulted. It does not explicitly contrast with update_offer or upload_offer_archive, but the create semantics are unambiguous.

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 conveys real usage context: only name is required, payout_type defaults to Auto meaning payout comes from the postback, and local offers require a ZIP with index.html at the root. However, it never states when to choose this over update_offer or upload_offer_archive, so routing guidance is only implied.

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