set_cpm

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

Description adds that the tool uses a modal and dry-run behavior by default, which is beyond annotations (readOnlyHint=false, destructiveHint=false). However, does not disclose potential side effects or auth requirements.

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?

Two sentences, no redundant information, essential points front-loaded. Every word adds value.

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?

While the tool is simple, the description lacks details about return value, behavior after execution, and parameter constraints. With low schema coverage and no output schema, more context would be beneficial.

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?

Only the confirm parameter is explained ('requires confirm=True to execute; default is dry-run'). No semantics provided for cpm or ad_id, despite 0% schema description coverage. Leaves agent guessing about parameter values.

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 'Set' and resource 'CPM' explicitly stated. Mention of '/edit_cpm modal' further clarifies the operation. Distinct from sibling tools like set_budget or create_ad.

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 when to use: requires confirm=True for execution, default is dry-run. Provides clear usage condition but lacks comparison to alternatives.

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