remnawave_external_squads_create

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

No annotations are present, and the description only labels the tool as a 'mutation'. It does not disclose behavioral aspects such as authorization requirements, side effects, or the role of the confirmToken and mutationApproved parameters. The agent has no insight into what happens when this tool is called.

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?

While the description is short, it is under-specified to the point of being unhelpful. Conciseness should not compromise substance; here it fails to convey essential information.

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's complexity (4 parameters, one nested object, no output schema) and the lack of annotations, the description is completely inadequate. The agent has no information on return values, error conditions, or how to use the tool effectively.

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 of the parameters (payload, confirmToken, responseMode, mutationApproved). The payload is an open object with no guidance on its structure. This leaves the agent unable to construct a valid call.

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 'external_squads.create (mutation)' which hints at creation but does not explicitly say what is created (e.g., 'external squad'). It is nearly a tautology as it restates the tool's method name. Contrast with high-scoring examples that use specific verb+resource constructions.

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 its many siblings (e.g., remnawave_external_squads_add_users, update, delete). There is no mention of context, prerequisites, or alternatives.

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