kadam_adv_update_campaign_folder

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

The description confirms a write operation, which is already indicated by 'readOnlyHint: false'. No additional behavioral traits (e.g., side effects, permissions, rate limits) are disclosed beyond the annotations.

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 sentence that conveys the essential purpose without any superfluous words. It is efficiently structured.

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 tool with 5 parameters and no output schema, the description is too sparse. It does not explain whether updates are cumulative or overwrite, nor does it provide enough context for an agent to use it effectively without additional insight.

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?

The description mentions 'budgets and distribution', which loosely maps to totalBudget, dailyBudget, and evenDistribution, but does not explain the 'limitsEnabled' parameter or the 'id' parameter. With 0% schema description coverage, more detail is needed to fully clarify each parameter's 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', the resource 'campaign group' (clarified as folder), and the specific settings 'budgets and distribution'. It distinguishes from sibling tools like 'kadam_adv_create_campaign_folder' and 'kadam_adv_update_campaign'.

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 it is used to update campaign group settings, but it does not explicitly state when to use it versus other update tools (e.g., 'kadam_adv_update_campaign_bid') or provide any exclusions or prerequisites.

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