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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered, and 'reconcile' is consistent with a read/compute operation (no contradiction). However, the description adds nothing beyond them: no indication of what is reconciled, whether a plan is persisted, or what the reconciliation produces.

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?

It is a single short fragment with no waste, but under-specification masquerading as conciseness. Nothing is front-loaded that would orient the agent before it reads the schema.

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 tool with a deeply nested request object, zero schema descriptions, and enum-like decisions (scope_policy strict/partial), this one-line fragment is far too thin. The output schema means return values needn't be explained, but purpose, sequencing vs. prepare siblings, and parameter intent are all missing.

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% across two top-level parameters, and the nested request object exposes seven properties (ad_account_id, target_campaign_id, requested_items, requested_budget_minor, scope_policy, currency) with no in-schema docs. The description mentions none of these, leaving parameter meaning entirely opaque.

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 largely restates the tool name ('Reconcile ... campaign plans') and adds only the opaque modifiers 'fixed existing-Ad' and 'before prepare'. An agent cannot tell what reconciliation actually means operationally, nor how it differs from the numerous campaigns_prepare_* siblings.

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?

'before prepare' is the only usage signal, and it references a phase, not a sibling tool (no 'prepare' tool exists by that name; the siblings are campaigns_prepare_budget_change, campaigns_prepare_status_change, etc.). No conditions, prerequisites, or alternatives are stated.

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