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

Annotations already declare readOnly/idempotent/no-destructive, and the description adds meaningful behavior beyond them: full pagination, the `_truncated: true` incompleteness caveat (with the warning never to claim the list is exhaustive), and the dynamic `_available_fields` key disclosure. These are the operational traits an agent actually needs.

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?

Front-loaded lead sentence followed by the field manifest and the two behavioral caveats. The long field enumeration is dense but informative; it is slightly verbose yet every clause carries operational or schema meaning.

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-parameter read tool with a rich output schema and complete annotations, the description over-delivers: return shape, pagination, truncation handling, and follow-up tooling are all covered. Nothing needed to invoke it correctly is missing.

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?

One required parameter (account_id) with 0% schema description coverage and no mention in the description. The name is largely self-evident, so the gap is small, but the description does not compensate for the missing schema documentation.

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 with scope: 'Lists ALL conversion tracking rules on a LinkedIn ad account'. The field inventory and the LinkedIn framing distinguish it from sibling conversion-list tools (list_conversion_actions, list_conversion_goals) that belong to other networks.

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?

Gives clear downstream usage: use the returned id with attach_linkedin_conversion / detach_linkedin_conversion, and names those alternatives explicitly. It lacks an explicit 'when not to use vs other list tools' exclusion, but the action context is well established.

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