get_monthly_budget_pacing

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: always scoped to current month, no date filter, 150-row cap, and required environment variables. It also explains the meaning of several output fields. This gives an agent good awareness of the tool's behavior, though it could mention whether results are sorted or if pagination exists.

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?

The description is well-structured with a concise opening sentence followed by bullet-pointed key fields. It is informative without being verbose. However, it could be slightly more concise by omitting the full bullet list and referring to the schema for field details (though no output schema exists). Overall, it earns its length.

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?

Given the tool's simplicity (optional params, read-only, no output schema), the description provides constraints, environment requirements, and field meanings. However, it does not specify the return shape (e.g., list of objects), how parameters affect the result, or error conditions. It is adequate but not fully complete for an agent to anticipate all outcomes.

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 0%, so the description must clarify parameters. It mentions 'all active campaigns' but does not explain the optional 'platform' and 'campaign_id' parameters or how they filter results. Without this, an agent cannot reliably use them. The description adds minimal semantic value beyond the 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?

The description clearly states the tool retrieves current calendar-month pacing status for all active campaigns from a specific BigQuery view. It lists key output fields, making the purpose specific and actionable. Though it does not explicitly differentiate from siblings like 'get_pacing_report', the detail and scope are sufficient for a clear purpose.

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 notes that the view is scoped to the current month with no date filter and requires specific environment variables. However, it does not provide guidance on when not to use this tool versus alternatives (e.g., other reporting tools) or indicate prerequisites beyond environment setup. Usage guidelines are implied but not explicit.

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