remnawave_public_subscriptions_get

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

With no annotations, the description must disclose behavioral traits. It only labels the operation as 'sensitive-read,' which hints at permissions but does not explain side effects, rate limits, or whether a mutationApproved parameter indicates potential write behavior in certain modes. This is insufficient.

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 very short (one sentence, 13 words), which is typically a positive for conciseness, but it lacks essential information. It cannot be considered well-structured when it communicates almost nothing about the tool's purpose or usage.

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 absence of annotations, output schema, and schema descriptions, the description is severely incomplete. It fails to explain return values, parameter semantics, or behavior details. The tool's complexity (4 parameters, one with enum, sensitive-read context) demands much more context.

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 0%, and the description does not explain any of the four parameters (payload, confirmToken, responseMode, mutationApproved). The presence of mutationApproved is confusing for a 'get' operation and requires clarification. The description adds no value beyond the 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 states the tool is for 'public_subscriptions.get' and labels it as 'sensitive-read,' but it does not specify what the tool actually retrieves or how it differs from closely related siblings like remnawave_public_subscriptions_get_by_client_type and remnawave_public_subscriptions_get_info. The purpose remains vague.

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 is provided on when to use this tool versus alternatives. There are no exclusions, prerequisites, or comparisons to sibling tools. The description offers no context for decision-making.

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