Configure RevenueCat

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

Beyond the general hints (destructive, read-write), the description specifies exactly what configuration secrets are managed. It adds functional context regarding the persistence of the `signing_secret` when omitted, which is a specific operational trait.

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, dense sentence that is perfectly sized and front-loaded. Every word contributes to defining the tool's scope and behavior.

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 rich annotations and detailed input schema, the description provides excellent coverage, defining the target of configuration and the logic behind key optional fields.

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 description explains the purpose of three of the five key parameters (provider app id, authorization secret, and webhook signing secret), adding semantic value beyond the basic strings defined in the input schema.

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 (Store/Configure) and the resource (RevenueCat provider app ID, authorization secret). It is highly specific and easily distinguishable from sibling tools like get_revenuecat or create_integration.

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?

It provides clear conditional guidance on the `signing_secret` parameter: if it is omitted, the currently stored secret will be maintained. This directs usage for that specific field.

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