optimization_baseline

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds the 28-day bounded window and policy scoping, but leaves open what 'bounded' means (row limits, data availability) and what happens when history is short — relevant for an openWorld read.

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?

A single front-loaded sentence with zero filler; the scoping qualifiers (bounded, 28-day, named policy) come before anything else.

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?

Output schema exists so return values needn't be described, but for a policy-scoped analysis tool the description omits the policy lifecycle context (valid policy sources, insufficient-data behavior) and does not explain the 'bounded' qualifier, leaving real gaps.

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 documents profile and adAccountId (67% coverage), and the description's 'for a named policy' implies the policy param is a reference to a named optimization policy, which adds a little meaning. It does not clarify the accepted policy identifier format or where to obtain it (e.g. optimization_policies_list).

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?

Specific verb and resource: builds a bounded 28-day Apple Ads performance baseline scoped to a named policy. An agent can tell it apart from siblings like optimization_plan or optimization_history by the 'baseline' framing, though the description never explicitly contrasts them.

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 when-to-use, when-not-to-use, or prerequisite guidance is given. Nothing says whether a baseline must precede optimization_plan, whether the policy must exist first, or what to do if there is insufficient 28-day history.

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