Google 広告のキャンペーン一覧を取得

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's '読み取り専用' is redundant. It adds useful context about status values (ENABLED/PAUSED, not ACTIVE) and that REMOVED are excluded, plus that daily budget only exists on campaigns. These are valuable behavioral details beyond annotations.

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?

Concise single paragraph with bold emphasis on key points. Front-loads the main purpose and critical constraints. No wasted 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?

Complete enough for a list tool: what it lists, status filtering behavior, budget location, and read-only nature. The absence of an output schema means return format isn't described, but that's a minor gap for a listing 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?

Schema description coverage is 100%, so the schema fully documents all three parameters including defaults and enums. The description adds no parameter-specific syntax or format details, so the baseline of 3 is appropriate.

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?

States a clear verb (list) and resources (campaign/ad group/ad), distinguishing it from creation/update siblings. However, it doesn't explicitly differentiate from google_ads_search, google_ads_report, or google_ads_keywords, which may also retrieve entities. Still, the scope is clear.

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?

Implies usage for listing campaigns, ad groups, and ads, but doesn't say when to prefer this over other read tools like google_ads_search or google_ads_report. No exclusions or prerequisites are mentioned.

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