set_navigation_mode

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

The description mentions that TREE and MIXED modes auto-build the sidebar, which is a behavioral trait. However, it does not disclose side effects of setting to NONE or STATIC, reversibility, or permission requirements. Without annotations, the description carries the full burden but only partially fulfills it.

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 long, front-loads the verb and resource, and provides the list of values and a key behavioral note. No extraneous information.

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 setter with one parameter and no output schema, the description is fairly complete: it explains the allowed values and the behavioral difference of two modes. It could mention default mode or error handling, but these are minor omissions.

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 input schema has 0% description coverage, so the description must compensate. It lists the allowed values and their effects, adding meaning beyond the schema's type string. However, it does not specify formatting, defaults, or that the parameter is required.

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 action ('Set') and the resource ('navigation mode'), lists all allowed values (NONE, TREE, MIXED, STATIC), and explains the behavioral implication of TREE/MIXED modes. This distinguishes it from siblings like get_navigation.

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 is provided on when to use this tool versus alternatives (e.g., get_navigation). There is no mention of prerequisites, context, or when not to use it.

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