read_tab_container

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

The verb 'Read' implies a non-destructive operation, but the description discloses nothing else: no return format, no preconditions, no side effects. With no annotations, this sparse description leaves significant behavioral ambiguity.

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 only a short fragment, but it is under-specified rather than economically complete. It fails to include useful context that would justify its brevity, making it too thin for an effective tool description.

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 output schema, the description should clarify what information the tool returns, but it does not. This leaves agents guessing about the tool's utility, output, and exact behavior, which is inadequate even for a simple read 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?

Both schema parameters (name, scene_path) have clear descriptions in the input schema, covering 100% of them. The tool description adds no additional parameter meaning or usage context beyond what the schema already provides.

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 'Read TabContainer/TabBar' identifies the tool's action and target resource, but it nearly duplicates the tool name and adds no detail about what reading entails. It distinguishes from sibling tools only by naming the node type, without explaining scope or purpose.

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?

There is no guidance on when to use this tool, what scenarios it fits, or how it compares to alternatives like read_container or read_ui_nodes. The description gives no context for selecting or switching between sibling tools.

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