get_suprsend_user_objects_subscriptions

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

Annotations set destructiveHint=true, but the description describes a read-only list operation with no destructive behavior. This contradiction misleads the agent. The description does add pagination details and return format, but the contradiction is a severe flaw.

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 concise with well-structured sections (purpose, when to use, when not to use, returns). Every sentence adds value, 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?

Given no output schema, the description covers return format and pagination. However, the annotation contradiction (destructiveHint=true) is not addressed, leaving ambiguity about the tool's behavior, which reduces completeness.

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 100% with descriptions for all 3 params. The description adds value by stating the default limit of 20, which is not in the schema, helping the agent understand pagination.

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 the tool lists objects a user subscribes to, with a specific verb 'List' and resource 'user subscriptions'. It distinguishes from sibling tools like get_suprsend_object_subscriptions and get_suprsend_user_list_subscriptions.

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?

Explicit 'When to use' and 'When NOT to use' sections with clear examples ('what does X follow?') and named alternatives for inverse and list subscriptions.

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