remnawave_subscriptions_get_by_uuid

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

The description labels the tool as 'sensitive-read', but the input schema includes parameters like 'confirmToken' and 'mutationApproved', which are atypical for a read operation and suggest possible mutation or confirmation flow. No explanation is given for these parameters or the behavioral characteristics beyond the label. Annotations are missing, so the description carries full burden but fails to provide adequate transparency.

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 extremely concise, consisting of a single line. However, it is too terse and omits critical details, making it under-specification rather than efficient conciseness.

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 has 4 parameters with no descriptions, no output schema, and many sibling tools for subscription retrieval, the description is grossly incomplete. It provides no information on how to use the tool, what the response contains, or how it differs from similar tools.

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 4 parameters with 0% schema description coverage. The description does not explain any of the parameters (payload, confirmToken, responseMode, mutationApproved), leaving their purpose and usage entirely unspecified. This severely hinders the agent's ability to correctly invoke the tool.

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 'subscriptions.get_by_uuid (sensitive-read)', which indicates it retrieves a subscription by UUID and is a sensitive operation. However, it does not explain what a subscription is or what the UUID represents. It minimally distinguishes from siblings via the name but lacks clarity on the resource type.

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?

No guidance provided on when to use this tool versus siblings like remnawave_subscriptions_get_by_short_uuid or remnawave_subscriptions_get_by_username. The description does not specify prerequisites or alternatives.

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