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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context about what the listing exposes (status, serving state, referenced post) and that the workspace is optional with a single workspace, but says nothing about pagination/limits even though a count parameter defaults to 50.

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 short lines, front-loaded with the core action and result fields, with the workspace note demoted to a secondary sentence. Slightly undermined by mixing German and English phrasing, but there is no wasted text.

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 values needn't be explained. However, for a 3-parameter listing tool with zero schema descriptions, the missing count/pagination and campaign_id semantics leave an agent guessing on filtering and result volume.

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 description must carry the parameter burden. It explains only workspace ('Slug des Kunden-Workspace, optional bei nur einem Workspace'); campaign_id is merely implied by 'bzw. einer Kampagne' and count/paging is not addressed at all.

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 creatives) plus the scope (account-wide or per campaign) and even the fields surfaced (status, serving state, referenced post). It does not explicitly distinguish itself from the sibling linkedin_creative_performance, so it stops short of a 5.

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 scoping ('des Accounts bzw. einer Kampagne') implies when the tool is appropriate, but there is no explicit when-to-use/when-not guidance and no mention of the closest alternatives such as linkedin_creative_performance or linkedin_update_creative_status.

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