remnawave_subscriptions_get_raw_by_short_uuid

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

Without annotations, the description carries the burden of disclosing behavior. It only labels the operation 'sensitive-read' but does not explain what makes it sensitive, any required permissions, or side effects. It fails to clarify whether the tool is read-only or what the output contains.

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—a single line—which is efficient but comes at the cost of missing critical information. It front-loads purpose and sensitivity but does not earn its place due to under-specification.

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 complexity (4 parameters, nested objects, no output schema, no annotations), the description is entirely inadequate. It does not explain how to use the tool, what the response looks like, or how it differs from numerous similar subscription tools. The agent would have insufficient context 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?

With 0% schema description coverage, the description must compensate but offers no explanation of the four parameters (payload, confirmToken, responseMode, mutationApproved). The short UUID input mechanism is unclear, and the meaning of 'raw' vs 'normalized' response mode is not described.

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 identifies the tool as retrieving raw subscription data by short UUID, and the 'sensitive-read' tag hints at its nature. This clearly distinguishes it from siblings that use other identifiers or return non-raw data. However, it lacks specificity about what 'raw' entails.

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?

The description provides no guidance on when to use this tool versus alternatives like remnawave_subscriptions_get_by_short_uuid or similar subscriptions methods. No prerequisites, context, or exclusion criteria are mentioned.

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