remnawave_external_squads_update

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

The description only labels it as a 'mutation' but does not disclose behavioral traits like required permissions, reversibility, side effects, or what the mutationApproved parameter implies. With no annotations, the description fails to provide sufficient behavioral context.

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 (one sentence), it is under-specified and sacrifices informative content for brevity. It does not earn its place as it repeats the tool name without adding value.

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 has 4 parameters including a nested payload, no annotations, and no output schema, the description is severely incomplete. It fails to explain what external squads are, what the update does, or how to use the parameters 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?

The description adds no information about the parameters. With 0% schema description coverage, the agent has no guidance on what the payload, confirmToken, responseMode, or mutationApproved fields mean beyond their types and defaults.

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 it is a mutation (update) on external squads, which distinguishes it from create, delete, get, etc. However, it does not explain what external squads are or what updating entails beyond the verb and resource.

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 create or delete. There is no context about prerequisites or scenarios for updating external squads.

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