direct_list_bidmodifiers

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

With no annotations provided, the description carries the full burden. It explicitly states 'READ-ONLY', which is a clear behavioral disclosure of no side effects. It also scopes to campaign-level and device categories, though it doesn't detail return format or error behavior.

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?

One sentence, front-loaded with verb and resource, then READ-ONLY. Every word earns its place with 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?

For a simple list tool with one parameter and no output schema, the description covers the essential purpose and read-only nature. It doesn't explain the output format, but the enumeration of categories implies what is returned. A small gap is the lack of explicit parameter explanation.

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 schema has 0% description coverage, so the description must compensate. The parameter name campaign_id and the description's 'campaign-level' make the meaning inferable, but the description doesn't explicitly explain the parameter, so it only partially compensates.

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 uses the specific verb 'List' and identifies the resource as 'campaign-level bid modifiers' with the scope 'mobile/tablet/desktop/demographics'. This clearly distinguishes it from sibling set/delete tools like direct_set_bidmodifiers and direct_delete_bidmodifiers.

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 READ-ONLY flag and 'List' verb clearly indicate this is for reading, not modifying. However, it doesn't explicitly name alternative tools for modifications, so it lacks explicit exclusions, but the context is clear enough.

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