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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real context by disclosing what is returned (ID, name, type, on/off status, attribution windows, attached campaigns), which matters because there is no output schema, but it says nothing about scope (all rules on the account vs. filtered), pagination, or permissions.

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 tight sentences with no filler, and the resource definition is front-loaded before the domain hint. The first sentence is a noun-phrase fragment rather than an action statement, which slightly weakens the opening.

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 read-only listing tool with no output schema, the description covers the important ground: what the objects are, which fields come back, and the key domain constraint about website-conversion campaigns. The main omission is scope/pagination behavior for the returned list.

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%, so folder, account, and language are already fully documented in the schema. The description adds no meaning beyond that, such as whether account scoping narrows the returned rule set — baseline 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?

Names the specific resource (conversion rules from Insight Tag / Conversions API) and enumerates the fields exposed, which distinguishes it from sibling listing tools like linkedin_campaigns or linkedin_ads. The verb is only implicit — it reads as a field inventory rather than 'List/retrieve all conversion rules' — and it does not explicitly name a sibling it is not.

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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named. The closing note that website-conversion campaigns need an attached rule implies the practical use case (auditing rule attachment) but leaves the agent to infer it.

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