yd_bid_modifiers_get

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

No annotations. Description lacks behavioral traits: no mention of read-only nature, auth needs, or what happens with empty parameters.

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?

Very short, no fluff, but under-specified given the complexity of the tool and sibling count.

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?

No output schema. Missing details on return values, pagination, errors, or limits. Incomplete for a data retrieval tool.

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 client_login has schema description (33% coverage). Description adds no semantics beyond names; doesn't explain that you can specify campaigns and/or ad groups.

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 the action 'Get' and resource 'bid modifiers' for campaigns or ad groups. Distinguishes from sibling tools like add, delete, set, toggle.

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 on when to use this tool vs alternatives among many siblings. No context on prerequisites or conditions.

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