add_suprsend_object_subscriptions

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

Disclosures beyond annotations: calling twice creates duplicate-looking entries, suggests checking existing state, mentions side effects (separate row per subscription). Aligns with destructiveHint: true and readOnlyHint: false.

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?

Well-structured with clear sections and front-loaded core action. Every sentence adds value, no fluff.

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?

Covers all aspects: return value, side effects, when to avoid, and cross-references other tools. No output schema, but description explains return. For a complex tool with nested parameters, it is 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 coverage is 100%, so baseline is 3. Description adds value by explaining recipients structure ('users by distinct_id, objects by object_type + id') and optional properties. However, it could be more explicit about the SuprSend recipient format.

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 action: 'Subscribe one or more users or other objects TO this object.' It distinguishes from siblings like get_suprsend_object_subscriptions and other subscription tools by specifying the direction and recipient format.

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 lists when NOT to use: removing subscribers (use API directly), mailing-list/segment membership (use Lists API), and preference changes (use per-user/preference tools). Provides clear alternatives.

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