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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations: the tool returns a framework guide, always includes a toc, and supports section-specific reads. This helps the agent know what kind of response to expect even without an output schema.

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 compact and front-loaded: content list first, then the critical call-to-action, then the parameter usage hint. Every sentence earns its place with no vague filler or repetition of schema details. It is dense but immediately scannable.

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 one-parameter, read-only reference guide with no output schema, the description is complete: it states what the guide covers, when to use it, that a toc is always included, and how to request a single section. An agent has enough context to select the tool and invoke it correctly without further investigation.

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 coverage is 100% with the single optional section parameter fully described via enum and description, so the baseline is 3. The description adds value by explaining the intended usage of the parameter: 'pass section= (see toc) for a focused read.' This tells the agent why and when to use the parameter, not just what it is.

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 identifies the tool as the operator's brand & PPC decision framework and enumerates its specific contents: margin spine, product postures, campaign structure/bidding, harvesting/negation logic, guardrails, and decision triggers. This distinguishes it from the many data-query and staging tools among its siblings. The imperative 'CALL THIS' makes its role as a decision guide unmistakable.

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 gives explicit, highly actionable usage guidance: call this before analyzing an account or proposing ANY optimization, covering bids, budgets, negatives, harvest, campaigns, and pricing. It also frames the tool as the 'default operating model,' making the priority clear. The section= hint adds a focused-use path rather than requiring a full read every time.

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