Get newsletter list subscriber import

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely non-structured context by naming the required OAuth scope (newsletter_lists:read), which an agent needs for auth planning; it still omits what the import record contains and whether a pending import is polled.

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 the purpose front-loaded and no padding. 'Reads account data' is mild filler that restates the read semantics already implied by 'Get' and by the annotations, keeping it just short of 5.

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?

There is no output schema, so the description should ideally explain what a 'subscriber import' is (a bulk import job, its status, counts). It leaves that to inference, though annotations plus the fully documented schema make the call itself unambiguous.

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 all three parameters (account, publication_id, newsletter_list_id) are documented in the schema with patterns and defaults. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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 (Get) and a specific resource (newsletter list subscriber import), and the resource name matches its sibling newsletter_list_subscriptions_create_import closely enough to imply the read counterpart of that import job. It is clear, but it never explicitly distinguishes itself from the create_import sibling or from get_newsletter_list_subscription.

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 description gives no when-to-use guidance: it does not say this returns a previously created import job, nor when to prefer it over get_newsletter_list_subscription or list_newsletter_list_subscriptions. 'Reads account data' is not a usage condition.

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