iam_chat_subscriptions

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

With no annotations provided, the description carries the behavioral disclosure burden. It clearly indicates a read-only operation that returns the active subscription if one exists, and the 'if any' phrasing conveys that no subscription results in an empty/null outcome. It does not detail error cases or side effects, but for a zero-parameter getter the core behavior is well disclosed.

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 a single, tight sentence with no wasted words. The main verb and object appear immediately, and the conditional 'if any' is placed at the end without obscuring the core purpose.

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 zero-parameter, read-only lookup with an output schema present, the description provides all necessary context. The agent can invoke the tool safely and interpret the result without additional guidance about arguments or return structure.

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 zero parameters, so the description need not explain parameter meanings. The baseline of 4 applies because there are no parameters to document, and the description appropriately focuses on the return value instead.

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 states a specific verb ('Return') and a precise resource ('this mailbox's active live chat subscription'), making the tool's purpose immediately clear. It also distinguishes itself from sibling chat actions like iam_chat_post or iam_chat_tail by focusing on subscription retrieval rather than message operations.

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 implies the tool is used to check whether a live chat subscription exists for the mailbox, and the 'if any' qualifier signals that absence is a valid outcome. However, it provides no explicit guidance on when to choose this over alternatives such as iam_chat_join or iam_chat_leave, nor does it mention prerequisites.

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