get_device_bid_adjustments

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

Explains bid_adjustment range (-100 to 900) and meaning of empty list, plus clarifies Microsoft's terminology for mobile. These details add value beyond the readOnlyHint annotation.

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 concise sentences, front-loaded with the core action, no unnecessary 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 simple read operation, existing output schema, and annotations, the description fully covers expected behavior, output interpretation, and cross-references the write counterpart.

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 100% with description 'The campaign id.' The tool description does not add extra semantic meaning beyond the schema, which is adequate.

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?

Clearly states it reads device bid adjustments for a campaign, lists specific devices (Computers, Smartphones, Tablets), and distinguishes from the sibling set_device_bid_adjustment.

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 mentions the sibling tool for setting adjustments, guiding when to use this read tool. However, no explicit when-not scenarios, but context is clear.

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