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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does note that a zero budget pauses the promotion ('zero pauses'), which is a useful side-effect disclosure. However, it does not state whether the call overwrites an existing budget, requires an existing promotion, or returns any confirmation, leaving significant behavioral gaps.

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?

The description is a single efficient sentence with a semicolon separating the main action from the key behavioral note. There is no redundant phrasing or filler. It front-loads the purpose and adds only one extra detail.

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?

Despite having only two parameters and no output schema, the description is too sparse for confident invocation. It omits prerequisites (e.g., content must exist), the effect of repeated calls, and what happens after success or failure. The cryptic 'zero pauses' also needs expansion to be actionable.

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%, so the description must add meaning to the parameters. It clarifies that daily_budget_cents is the 'daily promotion budget' and hints that zero has special meaning. It does not directly explain content_id, though the tool name implies it identifies the promotion target.

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 clearly identifies the action ('Set') and the resource ('daily promotion budget'), making the tool's purpose obvious. It distinguishes itself from siblings like create_account and publish because none of them relate to promotion budgets. The trailing 'zero pauses' is a behavioral note that does not obscure the core purpose.

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 description offers no guidance on when to use this tool versus the sibling tools, no prerequisites, and no context about whether the promotion must already exist. It does not name any alternative or exclusion condition. An agent would have to infer usage from the tool name and parameters.

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