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

With readOnlyHint/destructiveHint/openWorldHint already declaring the safety profile, the description still adds real value: it specifies the return payload ('Compact rows only: id, name, sourceKeys, maps') in the absence of an output schema, and states pagination behavior ('No pagination — orgs do not have enough labels to page'). The remaining text about dryRun/confirm and the ~10 minute Explorer delay describes the publish workflow rather than this tool, so it is context rather than this tool's own behavior.

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?

Purpose and scope are front-loaded in the first sentence, but roughly half the text is instructions for a different tool (publish_label_dimensions dryRun/confirm flow, merge semantics, 'do not resend the full list'). That material is useful workflow context yet dilutes a listing tool's description.

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?

Covers what an agent needs to call this correctly: the returned fields (substituting for a missing output schema), the absence of pagination, and the correct sibling tools for filtered/related operations. No material gap remains.

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% and there is a single optional slug parameter already fully documented in the schema ('Omit to auto-detect from your account (fails if you belong to multiple orgs)'). The description adds no additional parameter semantics, which is the expected baseline when the schema carries the burden.

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 all published engineered label dimensions') and immediately defines the returned concept ('merge + value map'). It also names the sibling it is not ('Not virtual dimensions — those use list_virtual_dimensions'), so an agent can disambiguate from list_virtual_dimensions and list_label_dimension_usages without opening either schema.

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?

Explicit routing: use list_label_dimension_usages before rename or delete, use publish_label_dimensions operations for edits, use list_virtual_dimensions for virtual dimensions. The read-only scope of this tool is clearly bounded against the mutation path.

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