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

The annotations already declare this a safe, idempotent, closed-world read. The description adds real behavioral context beyond them: that results are restricted to accounts selected at connect time, that the response carries default_account_id, and that all_accessible widens the reach. This is meaningful disclosure the annotations do not provide.

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?

Three short sentences, zero filler, front-loaded with the core purpose before the default-scope and parameter behavior. Every sentence earns its place.

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?

An output schema exists, so return-format explanation is not required; the description still usefully flags default_account_id. Together with the parameter clarification, an agent has everything needed to call this correctly.

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 0%, so the schema names all_accessible but never explains it. The description compensates by defining the parameter's semantics precisely (all_accessible=true returns every account the credential can reach), which is exactly the missing meaning.

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 (Lists) and resource (the user's connected LinkedIn ad accounts), cleanly separating it from the many other list_* sibling tools such as list_meta_ad_accounts or list_microsoft_accounts. It does not explicitly compare itself to those siblings, but the LinkedIn scope is unambiguous.

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 clarifies the default scope (only accounts selected at connect time) versus the all_accessible=true branch, which is useful conditional guidance. However, it names no alternative tools and gives no explicit when-not-to-use guidance, so it is implied rather than directive.

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