remnawave_internal_squads_create

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

With no annotations, the description carries full burden. It only labels the tool as a 'mutation', hinting at a write operation but omitting details like authentication needs, side effects, or status of the created squad. The minimal label 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?

At one sentence, the description is too brief given the tool has 4 parameters, including a nested object. It under-specifies key details and does not earn its place; conciseness should not come at the expense of necessary 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?

No output schema, 4 parameters (one complex object), and zero annotations. The description provides no information about return values, payload structure, or the effect of parameters, making the description completely inadequate for correct invocation.

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%, yet the description offers no explanation of any parameter (payload, confirmToken, responseMode, mutationApproved). It fails to add meaning beyond the schema, leaving the agent without guidance on parameter usage.

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 'internal_squads.create (mutation)', which identifies the verb (create) and resource (internal_squads). It distinguishes from sibling tools by name, but lacks any detail on what an internal squad is or what creation 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?

No guidance is provided on when to use this tool versus alternatives like remnawave_internal_squads_add_users or external_squads_create. The description does not offer any context on prerequisites or use cases.

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