google_ads_get_change_events

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

No annotations are provided, so the description carries the behavioral disclosure burden. It usefully discloses enforced constraints: 30-day date window and LIMIT <= 10000. However, it does not explicitly state read-only status, error behavior, ordering, or permission requirements.

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 filler. The core purpose is front-loaded, and the second sentence adds important API constraint information that justifies its place.

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 fetch tool with seven parameters, the schema handles most parameter documentation, and the description adds the key Google Ads constraints. It does not detail output shape or pagination, but 'Fetch recent change_event rows' adequately communicates the return concept given the context.

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 86%, so the schema already documents most parameters with defaults, formats, and bounds. The description adds the cross-parameter 30-day window constraint that is not fully visible in the schema, but it does not deeply explain filter parameters. Baseline 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 specific verb and resource: 'Fetch recent change_event rows.' It also names concrete constraints, making it clear this tool is dedicated to Google Ads change events. Among many sibling get_* tools, this uniquely identifies the change-event resource without ambiguity.

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 implies usage by resource name and adds useful API constraint context, but it does not explicitly state when to use this tool versus alternatives or when not to use it. No sibling differentiation or exclusion conditions are provided.

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