editor_set_tab_container_param

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It only states 'Set a property' without mentioning whether the change is irreversible, what happens on invalid properties, permissions required, or the return value. This is a significant transparency gap for a mutation tool.

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?

A single sentence that is direct and free of extraneous information. It fully communicates the tool's purpose without waste.

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?

For a simple 3-parameter setter with full schema coverage, the description provides minimal but sufficient context ('open scene'). However, it does not mention return behavior (no output schema) or error handling, and given the absence of annotations, the overall completeness is moderate but not severely lacking.

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 coverage is 100%, so the schema documents all parameters. The description adds no additional parameter meaning, and its only param-related examples ('mass', 'energy') are generic and potentially misleading for TabContainer. Baseline 3 is appropriate since the schema handles parameter semantics, but the description does not enhance them.

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 clearly states the verb 'Set' and the resource 'property on a TabContainer/TabBar node in the open scene', which precisely defines the tool's scope. This distinguishes it from sibling tools like editor_set_container_param that target other node types.

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?

The description implies usage when setting properties on TabContainer/TabBar nodes, but provides no explicit guidance on when to prefer this over similar siblings (e.g., editor_set_container_param) or any exclusions. The context 'in the open scene' is helpful but alternatives are not discussed.

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