game_manage_group

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

The description only lists actions without revealing side effects (e.g., 'clear_group' is destructive), required permissions, or return behavior. Annotations lack any behavioral hints, so the description carries the full burden.

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 very short (one sentence) but lacks structure and misses listing all actions. It is not as helpful as it could be while remaining concise.

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, and the description fails to mention what the tool returns (e.g., list for get_groups). No error conditions or behavioral details. Incomplete for a multi-action tool.

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 covers all parameters with descriptions. The tool description adds no extra meaning; it even underspecifies the 'action' parameter by not listing all values. Baseline 3 due to high schema coverage.

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 the tool can add, remove, or list nodes from a group, which clearly indicates the primary purpose. However, it omits the 'clear_group' action listed in the schema, making it incomplete.

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 siblings like game_get_nodes_in_group. No context on prerequisites or appropriateness.

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