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

Annotations already declare it is a non-destructive, idempotent, open-world write, so the safety profile is covered. The description adds the important business constraint (whole currency units, minimum 20 USD), but says nothing about permission/scope requirements, whether other fields are left untouched, or error behavior on invalid budgets.

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 naming the resource, the fields, and the budget constraint, with zero filler. Nothing would be lost by keeping it this short.

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 an 8-parameter mutation tool with no output schema, the description omits what happens on success (updated entity vs. ack), how the required adAccountId ties to accountId/profileId resolution, and whether a partial update leaves other settings intact. Adequate but leaves real gaps.

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?

At 50% schema coverage, name, endDate, adAccountId and dailyBudget have no schema descriptions. The description compensates for dailyBudget by supplying the unit convention and a 20 USD floor not present in the schema, but adds nothing for adAccountId, profileId/accountId disambiguation, or the endDate format.

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 concrete verb (Change) and resource (TikTok ad group) plus the three mutable fields, so it is clearly distinct from ads_set_status or ads_update_account. It does not name a sibling alternative, but the scope is 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?

Usage is only implied: an agent can infer this is for editing budget/end date/name rather than pausing (ads_set_status) or creating (ads_create_campaign). No explicit when-to-use, prerequisites, or exclusions are given.

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