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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful detail that the return is account-scoped rules plus KB docs, skills and ad accounts, but it says nothing about size, latency, whether absent rules are omitted, or how the 'skills' parameter changes the payload — behavior beyond the annotation is only partially disclosed.

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 opening with the verb and resource, with the parenthetical list kept tight. The enumeration is long but each item is informative, so there is little waste; it is not quite maximally crisp.

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?

With an output schema present, the description need not explain return values, and annotations cover the safety profile, so the remaining burden is scope and routing. Scope is well covered; the only real gap is the missing when-to-use guidance relative to the many sibling tools.

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?

There is one optional parameter with 100% schema description coverage ('skill names whose full content to include'), so the schema carries the semantics. The description mentions skills only as part of the returned contents and does not clarify the default (null) behavior or the cost of requesting full skill content, so it adds essentially nothing 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?

States a specific verb ('Returns') and resource ('this company's account context') and then enumerates the contents: standing rules (conversion events, funnel sources, targets, currency, scope), knowledge-base sheets/docs, skills, and connected ad accounts. Against siblings like query_campaign_performance or the propose_* family, an agent can tell this is the read-only configuration/context fetch without opening the schema.

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?

Usage is only implied: the description suggests this is the setup/grounding call, but it never says when to call it (e.g., before analysis or before proposing changes) or when to prefer query_campaign_performance or account_health instead. No exclusions or prerequisites are given.

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