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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so safety is covered. The description adds useful cross-tool context about what the tags mean downstream, but says nothing about pagination behavior, result ordering, or empty-page termination beyond what the schema already documents.

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, front-loaded with the operation and its return shape, followed by the one piece of downstream context that matters. No filler.

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?

With no output schema, the description usefully enumerates the returned fields, and annotations carry the read-only profile. The remaining gap is list_uid semantics and whether the listing paginates — the latter is at least covered in the schema.

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 coverage is only 50%: the 'page' param is well documented in the schema, but list_uid has no description and merely a pattern constraint. The description's 'of a mailing list' only weakly implies list_uid's role, adding nothing about its format (UID vs. list name/ID).

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 the fields of a mailing list') and even names the returned fields (label, tag, type, required), which separates it from list_lists and get_list. It stops short of explicitly naming which sibling to use when, but the resource is unambiguous.

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 second sentence implies usage — the tags are the keys needed when adding or updating subscribers — so an agent can infer this is a discovery step before add_subscriber/update_subscriber. It never states that workflow explicitly, nor any exclusions or prerequisites.

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