game_ui_tabs

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

Annotations are minimal (title only) so no contradiction. Description implies read/write ('get/set') but doesn't expand on side effects, permissions, or whether actions are idempotent. Adequate but not enriched beyond annotations.

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?

One sentence front-loading the component type and action. Efficient but could include the third action (set_title) without bloating.

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 4 parameters, 3 actions, and no output schema, the description is too minimal. It doesn't explain what each action returns, how to use index vs title, or any dependencies (e.g., TabContainer must be present). Incomplete for an agent to use confidently.

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 100% of parameters with descriptions. Description adds no extra meaning over schema. Baseline 3 applies since schema already documents each parameter adequately.

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?

Description states 'get/set current tab' which captures two of three actions. Missing 'set_title' action, but overall verb+resource is clear and distinct from siblings (e.g., game_ui_control deals with generic UI elements).

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 game_ui_control or game_ui_item_list. Lacks context on whether it's for reading vs modifying tabs or prerequisites like node existence.

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