google_ads_get_bidding_strategies

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It usefully states that metrics are returned only when startDate/endDate are provided, otherwise only structure is returned. It does not disclose read-only guarantees, pagination, or error behavior, but the key conditional behavior is surfaced.

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 with no wasted words. The resource is named first, and the critical conditional behavior is stated concisely. Every sentence 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?

For a straightforward list tool, the description covers the essential behavioral distinction and names the resource. It does not detail the output shape, paging, or auth requirements, but the schema covers the parameters and defaults, so the dscription is sufficiently complete for selection and invocation.

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 description coverage is high at 80%, and the schema already documents startDate and endDate as 'for metrics'. The description essentially repeats this conditional relationship without adding new parameter meaning. It does not clarify typeFilter values or limit behavior beyond what the schema provides.

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 states a specific action on a specific resource: 'List portfolio bidding strategies.' This clearly distinguishes it from sibling tools like google_ads_get_campaigns or google_ads_get_budgets, and the 'portfolio' qualifier adds important scope.

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 description provides clear contextual guidance: use this tool to list portfolio bidding strategies, and include dates if metrics are needed. It does not explicitly name alternatives or when-not-to-use cases, but the scoped resource and conditional date behavior make the intended usage clear among the sibling tools.

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