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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds scope ('available on a connected profile') and enumerates the returned fields, which is useful given there is no output schema, but it says nothing about pagination, empty results, or connection/auth failure behavior.

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?

Two sentences with zero filler: the identification of the resource and its return fields comes first, and the downstream workflow hint second. Nothing is redundant with the title or schema.

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 single-optional-parameter read tool, the description plus annotations cover the essentials, and listing the returned fields compensates for the absent output schema. Minor gaps remain around empty-result and no-connection behavior, but nothing blocks correct invocation.

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 description coverage is 100% and the single `profile` parameter is already well documented in the schema, including the note that person names are ignored and the workspace's shared connection is used. The description adds nothing beyond 'on a connected profile', so the baseline of 3 applies.

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 and resource ('List the LinkedIn Ads accounts') and scopes it to a connected profile, which cleanly separates it from sibling listers like list_ad_campaigns and list_profiles. It also names the returned fields (id, name, status, currency), so an agent knows exactly what this tool yields.

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 sentence 'Use the returned id as `ad_account_id` in the other ads tools' clearly establishes this as the entry point for the ads tool family, which is real usage context. It does not state prerequisites (e.g., a LinkedIn Ads connection must exist) or what to do if the list is empty, so it stops short of full when/when-not guidance.

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