direct_set_bidmodifiers

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

Without annotations, the description discloses the write nature via 'WRITE' and the 0=exclude semantic, which adds some behavioral context. However, it repeats the allow_write requirement already present in the schema and does not discuss overwrite/merge behavior, error handling, or rate limits.

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 dense sentence, front-loaded with 'WRITE' and the data format. Every word earns its place, with no filler or 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 the lack of annotations and output schema, the one-liner is insufficient for a 4-parameter mutation tool. It omits when to use this tool, what the response looks like, and how dry_run/project interact, leaving critical gaps for an AI agent.

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 adds the important '0=exclude' semantic for bid_modifier, going beyond the schema's numeric range. However, it mostly repeats schema details (array structure, allow_write) and does not compensate for the 50% schema coverage by clarifying dry_run or project parameters.

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 explicitly states 'WRITE: bidmodifiers.set' with the payload structure and bid_modifier range, clearly identifying the operation and resource. It distinguishes from sibling tools by naming the bidmodifiers resource and the set operation, even though it doesn't describe the exact target entity type.

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?

No guidance is provided on when to use this tool versus alternatives like direct_set_device_bid_modifiers or direct_set_retargeting_bid_modifier. The description only states the operation and write guard, leaving tool selection and any preconditions unaddressed.

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