hide_advanced_tools

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

No annotations are provided, so the description carries the full burden. It discloses the core behavior (hides advanced tools) and importantly states that the action is reversible via 'show_advanced_tools.' However, it omits details such as persistence scope (session vs. global) or any side effects, though these are minimal for a toggle tool. The transparency is good but not exhaustive.

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 highly concise: two short sentences that immediately convey the action and the reversal mechanism. It is front-loaded with the primary purpose and contains no filler or redundancy.

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?

Given the tool's simplicity (zero parameters, no output schema, simple toggle behavior), the description is complete. It explains what the tool does and how to restore the previous state, which fully satisfies the context for an agent deciding to use it.

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 is empty, and there are no parameters. The description adds no parameter information, but none is needed. With zero params, the baseline is 4, and the description adequately serves its purpose without redundant detail.

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 tool's purpose: 'Hide advanced tools to simplify the tool list.' It uses a specific verb ('hide') and resource ('advanced tools'), and directly distinguishes itself from the sibling tool 'show_advanced_tools' by referencing how to undo the action.

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 explicitly names the alternative tool 'show_advanced_tools' for reversing the hide action, providing clear guidance on when to use this tool versus its counterpart. It also implies the primary use case (simplifying the tool list) with no ambiguity.

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