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 by structured data. The description adds useful context about what fields each item carries, but says nothing about pagination behavior, result limits, or pagination-relevant use of the limit parameter beyond what already exists in the schema.

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?

The description front-loads the action, follows with compact context, and closes with the one parameter that most needs clarification. Three sentences with little waste, though the middle motivation sentence is somewhat tangential to selecting or invoking the tool.

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 need not be explained, and the readOnly/openWorld annotations carry the safety profile. For a two-parameter list tool the main remaining gap is the undocumented limit parameter and lack of pagination guidance, keeping it at adequate-but-incomplete.

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 carries the burden. It usefully explains workspace ('Slug des Kunden-Workspace, optional bei nur einem Workspace'), compensating for one parameter, but the limit parameter (default 50) is left completely undocumented in both schema and description, leaving a real gap.

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 ('Custom Conversions des Werbekontos auflisten') and enumerates what is returned (Regel, Ereignistyp, Wert), so an agent can tell this is a read/list operation on custom conversions. It does not explicitly contrast with the sibling meta_create_custom_conversion, but the list-vs-create distinction is inherently clear.

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 'Ohne definierte Custom Conversion lässt sich nur auf rohe Pixel-Ereignisse optimieren' supplies the motivating context for why one would fetch this data, and the workspace note implies scope. However, there is no explicit when-to-use / when-not, and no routing to alternatives such as meta_list_pixels for raw event inspection.

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