get_suprsend_user_list_subscriptions

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

Description describes a read-only list operation, but annotations include destructiveHint=true, which contradict. The description does not disclose any destructive behavior, leading to a contradiction.

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?

Description is two well-structured paragraphs with clear sections (purpose, usage, returns). Every sentence adds value with no redundancy.

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?

Description explains returns (paginated list metadata) and default limit, but lacks details on pagination mechanism or metadata structure. Adequate for a reasonably complete tool given no output 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 covers 100% of parameters with descriptions. Description adds default limit hint (20) and mentions raising for larger results, providing useful context beyond schema.

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?

Description clearly states the tool lists SuprSend Lists a user belongs to, defines lists as workspace-level recipient groups distinct from object follows, and uses specific verb 'List' with resource 'SuprSend Lists'.

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?

Explicitly provides when to use (user asks about mailing lists or segments) and when not to use (object follows, followers of an object), naming specific alternative tools.

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