ghl_ad_li_reporting_list

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, signaling a safe read operation. Description adds endpoint and OAuth scopes, which provide some behavioral context but no additional details about rate limits, pagination, or response structure.

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?

Description is concise with front-loaded purpose. Includes technical details (endpoint, version, OAuth) that may be helpful but are not essential. No redundant sentences.

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 6 required parameters and no output schema, the description lacks important context: how parameters interact (e.g., campaignId and campaignGroupId both required? Can they be used together?), pagination behavior, default sorting, or what fields are returned in the response.

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%, so baseline is 3. Description does not add any extra meaning beyond what the schema provides (e.g., explaining relationships between campaignId and campaignGroupId, or clarifying that both are required).

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?

Description clearly states it retrieves a list of LinkedIn campaigns/campaign groups with reporting data. The verb 'Retrieve' and resource 'list' are specific. However, it doesn't explicitly distinguish between listing campaigns vs. campaign groups, or clarify that it returns multiple items vs. a single report.

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?

No guidance on when to use this tool vs. alternatives like ghl_ad_li_reporting_get (for a single report) or Facebook/Google reporting lists. No mention of use cases, prerequisites, or exclusions.

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