ghl_ad_li_account_list

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

Annotations already provide readOnlyHint, idempotentHint, and non-destructive. Description adds endpoint, version header, and OAuth scopes, giving useful behavioral context without contradicting annotations.

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?

Very concise: two lines for purpose plus additional technical details. Front-loaded and no wasted words.

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?

Lacks return type or output format details, which would be helpful for a list tool. However, with readOnlyHint and openWorldHint, the behavioral risk is low, and parameters are fully described in schema.

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 covers both parameters (locationId, isDraft) with descriptions. Description adds no extra parameter info, so baseline 3 is appropriate.

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 'Get LinkedIn ad accounts' and 'Retrieve LinkedIn Ads accounts available for the connected user'. Purpose is specific and distinguishes from sibling tools like 'get' and 'delete' via the 'list' verb, though not explicitly compared.

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?

Implied usage for listing accounts under the connected user, with endpoint and OAuth scopes provided, but no explicit when-to-use or when-not-to-use compared to alternatives like ghl_ad_li_account_get.

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