remnawave_profiles_get_computed

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

The description only labels the tool as 'read', but the input schema includes mutation-related fields (mutationApproved, confirmToken), which suggests potential side effects not disclosed. No behavioral traits beyond the read hint are described.

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 short, but it under-specifies the tool. It lacks essential details and does not earn its place as a standalone description.

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 four parameters, no output schema, and many sibling tools, the description is completely inadequate. It provides no context about computed profiles, return values, or parameter behavior.

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 provides no explanation for any of the four parameters (payload, confirmToken, responseMode, mutationApproved). The agent has no semantic understanding of what to input.

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 vaguely states it's a read operation on profiles, but 'computed' is undefined. It does not distinguish from sibling tools like remnawave_profiles_get or remnawave_profiles_list, leaving the agent without a clear purpose.

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 is no mention of context or exclusions, leaving the agent to guess.

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