yougile_set_chat_subscribers

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

The annotations already indicate non-read-only and non-destructive hints, but the description adds the key behavioral detail that the existing list is replaced, not merged. This goes beyond the simple 'set' phrasing and clarifies that any users not in the new list will be unsubscribed.

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 two short sentences, front-loaded with the action verb and resource. Every word adds value, and the critical 'Replaces existing list' clause earns its place. There is no unnecessary fluff or repetition.

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?

For a simple tool with two well-documented parameters and no output schema, the description provides sufficient context. It states what the tool does and the key override behavior. Minor gaps like whether an empty list is allowed or what is returned are not critical for such a straightforward setter.

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% (taskId and userIds both have descriptions), so the baseline is 3. The description adds context that userIds represent the complete replacement set, not an incremental update, which strengthens the semantic meaning beyond the schema's 'Array of user UUIDs to subscribe'.

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 uses the specific verb 'Set' and identifies the resource ('list of users subscribed to a task's chat notifications'), making the tool's purpose unambiguous. The phrase 'Replaces existing list' also distinguishes it from sibling tools like the getter yougile_get_chat_subscribers.

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 clearly indicates this is a full-replacement operation ('Replaces existing list'), which tells the agent when to use it and what to expect. While it doesn't explicitly name an alternative, the only sibling is a getter, so the usage context is clear without needing an explicit exclusion.

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