x_api_create_activity_subscription

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

With no annotations, the description fully bears the transparency burden. It discloses high-risk mutation, required permissions and auth scopes, environment-selection behavior, common failure conditions, and a safety warning. This is rich behavioral context beyond what structured fields provide.

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 well-structured with labeled sections and front-loaded with the core purpose. The 'Use when' line is somewhat redundant with the first sentence, but every other section contributes meaningful information without excessive verbosity.

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 the tool's complexity, lack of output schema, and 7 undocumented parameters, the description is remarkably complete. It provides expected response shape, failure conditions, required permissions, environment-selection details, and a concrete example, covering the major operational aspects.

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 0%, so the description must compensate. It explains the relationship between scopeTenantId, scopeUserId, scopeAccountId, and credentialKey, and clarifies that body holds the request payload. However, authorizationKey and preferredAuthType are only minimally addressed, leaving some gaps.

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 opens with 'Create X activity subscription,' a clear verb+resource combination. However, it does not differentiate this from sibling tools like x_api_create_account_activity_subscription, so it is clear but lacks explicit sibling differentiation.

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 explicitly states when to use ('Create X activity subscription') and provides a 'Do not use when' section naming alternatives such as x_schema_discovery and x_query_suggestion. It also lists recommended prerequisite and follow-up tools, giving strong usage guidance.

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