remnawave_internal_squads_get

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

Only mentions 'read', implying non-destructive behavior, but no annotations provided. No details on permissions, side effects, or return behavior. For a tool with no annotations, the description should offer more transparency.

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?

Extremely concise but under-specified. A single line does not provide sufficient information to be useful. Not a model of efficiency.

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 no annotations, no output schema, 4 parameters none described, and a vague purpose, the description is highly incomplete for a tool with this complexity and sibling count.

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 does not explain any of the 4 parameters (payload, confirmToken, responseMode, mutationApproved). The description adds no value beyond the schema.

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 'read' operation for 'internal_squads.get', which implies retrieving a specific squad. However, it does not clarify what an internal squad is, and the description is minimal. It distinguishes from sibling list and create tools, but could be more specific.

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 on when to use this tool versus alternatives like list or create. The description does not specify the purpose or context for usage.

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