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

Annotations already declare this is a non-read, non-idempotent, non-destructive mutation. The description usefully adds the auth/dependency context (authenticated buyer, funded placement), but does not disclose the side effects of 'enabling' a campaign, what happens on repeat calls given idempotentHint=false, or what state the profile ends in.

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 sentences with zero filler. The primary action is front-loaded and the dependency/environment note follows immediately; nothing could be cut without losing signal.

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 7-parameter mutation with deep nested objects and no output schema, the description covers the action and its preconditions but omits the outcome and side-effect profile. An agent can attempt the call but cannot predict what changes or what a repeated invocation does, which is a real gap for a non-idempotent write.

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 100% and every parameter, including the nested brand_rules structure, is documented inline. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 specific verbs ('configure', 'enable') and resources ('native brand profile', 'booked reactive campaign'), so an agent knows this is a write operation linking brand config to a campaign. It does not, however, differentiate itself from closely named siblings like generate_brand_creative, import_feedback_creative, or review_feedback_creative, so routing still requires inference.

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 second sentence implicitly states prerequisites — an authenticated native buyer and an existing funded placement — which tells the agent when the call will succeed. It stops short of naming when to use this versus generate_brand_creative or create_creative_experiment, and gives no exclusions.

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