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

The description adds behavioral context beyond the readOnlyHint annotation by specifying that it returns ad accounts from Meta Ads, Google Ads, LinkedIn Ads, TikTok Ads, etc. It does not contradict annotations and provides useful details about the data content.

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 two sentences, front-loaded with the main purpose, and each sentence adds a piece of information (scope and platform examples). It is appropriately concise with no redundant fluff.

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 simple read-only list tool with one optional parameter and no output schema, the description adequately conveys the purpose and expected data (ad accounts from various platforms). It doesn't mention pagination or edge cases, but the tool's simplicity and schema coverage make this acceptable.

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?

The input schema fully describes the optional 'platform' parameter with an example, achieving 100% schema coverage. The description adds no additional parameter-specific meaning, so it relies on the schema, which is sufficient for the baseline.

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 states the tool lists all connected advertising accounts across platforms, with a specific verb ('List') and resource ('advertising accounts'). It distinguishes from sibling tools like list_connected_accounts by its advertising-specific focus, and the second sentence clarifies supported platforms.

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 implies when to use it (when you need ad accounts) but does not explicitly state when to use this over alternatives like list_connected_accounts or list_ad_campaigns, nor does it provide exclusions or prerequisites.

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