kadam_adv_create_autorule

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

Annotations already indicate readOnlyHint=false, so the description correctly implies mutation. Adds CPC-only constraint and bidChange formula, which enriches behavioral understanding. Does not discuss validation errors, idempotency, or authorization, but given annotation presence, the bar is lower and the added context is valuable.

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?

Three efficient sentences front-load main purpose. Every sentence adds unique value: first defines action and restriction, second explains usage pattern, third details special parameter requirements. No redundancy.

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 tool complexity (12 parameters, conditions array, business logic), the description covers key aspects: CPC-only, strategy pattern, bidChange specifics. Does not explain conditions structure or other rule types, but schema covers those. No output schema is acceptable. Good balance for high schema coverage.

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 coverage is 83%, high. Description adds critical semantics for bidChange rules: relationship between bidRate, bidMax, EPC, and the formula. Also clarifies that bidRate=1 is valid. This goes beyond schema descriptions, justifying a score above baseline 3.

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?

Clear verb+resource: 'Create an autorule on a CPC campaign'. Adds context that autorules are CPC-only and that campaigns usually carry several rules, distinguishing this from other campaign types and defining usage pattern.

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?

Explicitly states CPC-only constraint and pattern to call once per rule. Provides specific details for bidChange rules. However, does not explicitly contrast with siblings list (e.g., update_autorule, set_autorule_status) or state when not to use.

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