kadam_adv_update_campaign_folder

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

Annotations indicate readOnlyHint=false, and the description confirms a write operation ('Update'). However, it does not disclose behaviors like required permissions, side effects on other settings, or result format, leaving gaps beyond what annotations provide.

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 5-word sentence, very concise. However, it is arguably too brief to be fully helpful, but it earns points for efficiency and no wasted words.

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?

Given the 5 parameters and no output schema, the description is incomplete. It does not explain parameter purposes, constraints (e.g., budget limits, required id), or return behavior (success/failure), making it insufficient for an agent to invoke correctly.

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 0% schema description coverage, the description must compensate. It only mentions 'budgets and distribution', hinting at some parameters (totalBudget, dailyBudget, evenDistribution), but leaves out 'id' and 'limitsEnabled' entirely and provides no constraints or types, adding minimal meaning.

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 states the verb 'Update' and the resource 'campaign folder', and specifies the scope 'budgets and distribution', distinguishing it from sibling tools like 'create' or 'list' operations.

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 implies usage for modifying folder budgets and distribution, but lacks explicit guidance on when to use this tool over alternatives (e.g., update_campaign, update_campaign_bid) or when not to use it.

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