iyke_mode

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

No annotations are provided, so the description must bear the full burden. It states the action but does not disclose behavioral traits such as whether the switch is immediate, if there are side effects, or if permissions are required. The impact is minimal but could be clearer.

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 two sentences, front-loads the verb and resource, and includes all necessary information without extraneous text. Every sentence earns its place.

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 tool with one enum parameter and no output schema, the description adequately covers the purpose and valid inputs. It could mention if the tool returns a success message, but that is not essential.

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?

The description adds semantic value beyond the schema by categorizing modes as 'core' vs 'mini-apps', which helps in selecting the correct value. Since there is only one parameter with an enum, this extra context is beneficial.

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 uses the specific verb 'Switch' and resource 'activity-bar sidebar mode'. It lists all valid modes and distinguishes between core and mini-apps, making the purpose clear and distinguishable from sibling tools that have different functions.

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 to switch sidebar modes and lists valid options, but it does not provide explicit guidance on when to use this tool versus alternatives like iyke_open or iyke_focus. No exclusions or context are given.

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