subscription_group_versions_create_instance

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

No annotations are provided, so the description carries the full burden, and it discloses nothing: no note that this is a mutating create, no permission/scope requirements, no mention of what happens on success or failure, no side effects. Pointing at an OpenAPI schema is not behavioral disclosure.

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?

It is short, but the POST route is duplicated verbatim inside parentheses and the only substantive content is an external schema pointer, so the single sentence does not fully earn its place. Not bloated, but wasteful 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 create endpoint with a nested JSON:API body, no annotations, and no output schema, the description should at minimum explain the envelope and the parent linkage. Deferring entirely to an OpenAPI component leaves the agent without enough to invoke it correctly.

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?

There is only one parameter and schema description coverage is 100%, so the schema already documents the body. The description merely repeats the schema reference (components.schemas.SubscriptionGroupVersionCreateRequest) without adding format, required-field, or envelope guidance, which is the baseline for high coverage.

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 only echoes the HTTP route 'POST /v1/subscriptionGroupVersions' and never states in plain language what the tool does (create a subscription group version) or what a subscription group version is. It is effectively a machine-generated restatement of the name/endpoint rather than a purpose statement.

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?

There is no guidance on when to use this tool versus siblings like subscription_groups_create_instance, subscription_group_versions_get_instance, or subscription_versions_create_instance. No prerequisites, no context about the parent resource that must exist first.

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