get_suprsend_user_list_subscriptions

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

The description states 'List' implying a read-only operation, but the annotations include destructiveHint: true and readOnlyHint: true, which are contradictory. The description does not resolve this inconsistency, and according to rules, a score of 1 is given when description contradicts annotations.

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?

The description is highly concise, using three clear paragraphs: purpose, usage guidelines, and return info. Every sentence adds value, and the structure is front-loaded with the core functionality.

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?

Without an output schema, the description explains returns as 'a paginated list of List metadata' and mentions pagination and default limit. While the metadata structure could be detailed further, the description is adequate for basic understanding and use, given the tool's complexity.

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?

The input schema has 100% coverage with parameter descriptions. The description adds value by noting the default limit of 20 and suggesting to raise it for larger results, which goes beyond the schema. This justifies a score above the baseline of 3.

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?

The description clearly states 'List the SuprSend Lists this user belongs to' and distinguishes lists from object follows. It specifies the resource (user's list subscriptions) and action (list), providing a specific verb+resource combination that 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 description provides explicit when-to-use examples ('what mailing lists is X on?') and when-not-to-use guidance with direct references to sibling tools (get_suprsend_user_objects_subscriptions, get_suprsend_object_subscriptions). This is exemplary usage guidance.

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