remnawave_external_squads_get

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

The description only notes '(read)', implying a non-destructive operation, but no annotations exist to confirm this. It provides no details about permissions, side effects, or required setup. Given the lack of annotations, the description carries the full burden and fails to inform adequately.

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 a single sentence, but its brevity comes at the cost of essential information. It is underspecified rather than concise, providing no value beyond the tool name.

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?

With 4 undocumented parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain how to use the tool, what it returns, or any constraints, making it virtually unusable for an AI agent.

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 but the description explains none. With 0% schema description coverage, the agent lacks any guidance on what to pass, especially the 'payload' object which likely contains critical identifiers. The 'mutationApproved' field is confusing for a read operation and is not explained.

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 'Remnawave external_squads.get (read)' is a near-tautology of the tool name. While it adds the '(read)' hint, it does not specify what the tool retrieves or how it differs from siblings like 'list' or 'create'.

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 such as 'remnawave_external_squads_list' or other read tools. The agent has no context to choose appropriately.

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