List newsletter list subscriptions

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, but the description adds a genuinely useful layer beyond them: 'Reads account data' and the required OAuth scope newsletter_lists:read. Those are auth/context disclosures the annotations cannot express, though nothing is said about pagination behavior or result size.

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?

Three short sentences with zero filler; the action, the data reading, and the auth requirement are front-loaded in that order. Nothing could be removed without losing information.

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 paginated list tool with no output schema, the description says nothing about what a subscription record contains or how pagination/continuation cursors behave, though the schema covers the pagination mechanics. The auth and account-reading notes make it minimally adequate rather than complete.

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%, including detailed guidance on cursor vs deprecated offset pagination, limit bounds, and all_pages/max_items. The description adds no parameter-level meaning, so the baseline 3 is appropriate.

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?

Names a specific verb+resource (list newsletter list subscriptions) that is clearly narrower than the sibling list_subscriptions and distinct from get_newsletter_list_subscription. It does not explicitly contrast itself with those siblings, so an agent must infer the difference from the name alone.

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?

No when-to-use guidance, no exclusions, and no alternatives named. The auth note ('OAuth integrations require newsletter_lists:read') is a prerequisite, not a routing rule, so the agent gets no help choosing between this and list_subscriptions or the single-subscription getter.

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