daily_budget_recommendations

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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the safety profile is covered structurally; the phrase 'without applying them' reinforces that no mutation occurs, which is useful confirmation. It does not disclose where recommendations originate, whether they are account-wide or per-campaign, or any freshness/staleness behavior that would help interpret results.

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 no filler; the key constraint ('without applying them') arrives immediately. It is arguably under-specified rather than padded, so conciseness itself is not the problem.

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?

An output schema exists, so return values need not be explained, and the required profile/adAccountId are schema-documented. However, for a nine-parameter reporting-style tool with many optional shaping parameters, the description says nothing about what the recommendations represent or how filtering affects them, leaving the agent to infer behavior from the schema alone.

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 all nine parameters (fields, filters, groupBy, timeRange, pagination, adAccountId, profile, etc.) are already documented in the schema. The description adds no parameter meaning beyond that, which lands exactly at the baseline for a fully documented schema.

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 (read) plus specific resource (daily-budget recommendations), with the added qualifier 'without applying them' that separates it from the apply_preview and dismiss_preview siblings. It stops short of naming those siblings, so differentiation is implied rather than explicit.

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?

'Without applying them' signals this is the inspection-only path and gestures at the apply/dismiss alternatives, but it never states the condition under which an agent should choose this over daily_budget_recommendation_apply_preview or daily_budget_recommendation_dismiss_preview. Usage is inferable, not spelled out.

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