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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=true, so the safety profile is covered. The description adds the returned fields (uid, name) and the downstream campaign use case, but says nothing about pagination behavior, result sets, or empty-page semantics that a caller must know.

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 short sentences with no waste; the resource being listed and the returned fields are front-loaded, and the campaign-uid note follows logically.

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?

No output schema exists, so the description usefully names the return fields (uid, name). Pagination is handled by the schema's page description. The main gap is not explaining how to obtain list_uid, which matters for a required parameter.

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 50%: the 'page' parameter is well documented in the schema, but 'list_uid' has no schema description, and the description only refers vaguely to 'a mailing list' without explaining the uid format or how to obtain it (e.g., from mailblaze_list_lists). Marginal compensation for the coverage 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 ('List') and resource ('segments defined on a mailing list') and names the returned fields (uid, name). It is distinguishable from siblings like list_list_fields and list_lists, though it doesn't explicitly contrast with them.

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?

'A segment uid can be used when creating a campaign' gives a downstream-use hint, which implies why an agent would call this. However, there is no explicit when/when-not guidance or mention of the alternative tools such as mailblaze_create_campaign or mailblaze_list_list_fields.

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