Create subscription availability

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

Annotations do not indicate readOnly or destructive hints, so the description adds value by revealing the dependency on create-subscription-price and the specific 409 error consequence. It does not mention idempotency or other side effects, but the provided context is meaningful beyond annotations.

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 sentences, front-loaded with the primary purpose and immediately followed by critical usage guidance. No wasted words.

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?

The tool is simple (3 params, no output schema) and the description covers the essential ordering constraint. The availabilityInNewTerritories parameter is documented in the schema, so the description need not repeat it. The context is complete for correct invocation.

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 description coverage is 100%, so the baseline is 3. The description itself does not elaborate on parameters beyond what the schema already includes; the schema's 'territoryIds' description already mentions list-territories and the relationship to create-subscription-price. No additional parameter insight is provided.

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 a specific verb and resource: 'Set which territories the subscription is available in.' This clearly distinguishes it from sibling tools like create-subscription-price and create-subscription, while also noting a critical relationship to create-subscription-price.

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?

Explicit usage guidance is provided: 'Call this before create-subscription-price; otherwise adding a price often returns 409 ENTITY_ERROR.RELATIONSHIP.INVALID.' This tells the agent when to use it, the ordering requirement, and a concrete failure mode if not followed.

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