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

The description provides significant behavioral context beyond the annotations (readOnlyHint). It lists specific data returned (Name, Status, Total Budget) and, crucially, explains a nuanced behavioral trait of the 'workspace' parameter: it is optional only when the user has a single workspace.

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 highly economical. The first sentence defines the 'what', and the second sentence defines the 'how' and the organizational context, both being necessary information delivered efficiently.

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 low parameter count and low schema coverage, the description provides comprehensive contextual completeness. It covers the resource, the data contained, and the specific logic for the primary scoping parameter.

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?

Since schema description coverage is 0%, the description must carry the load. It excels by explaining the semantic constraint on the 'workspace' parameter (optionality based on count), which adds vital meaning beyond the simple string/null type defined in 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 tool clearly states its purpose: retrieving LinkedIn campaign groups. It names the specific resource and scope ('Campaign Groups of the Ad Account') and provides immediate context regarding the hierarchy (CG -> Campaign -> Creative), successfully differentiating it from other listing tools.

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 tool provides strong contextual usage guidance by mapping its place in the advertising hierarchy. While it does not explicitly state, 'Do not use this for listing individual ads,' the hierarchical definition strongly implies the correct use case.

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