Open or close a sidebar

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

The description discloses specific behavioral constraints that go beyond the basic annotations, notably that certain actions ('open' and 'toggle') require an 'id,' while 'close' does not. It also provides the specific measured entry point for implementation context.

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 definition is highly concise. It packs three distinct pieces of information—the actions, the prerequisite data source, and the parameter dependencies—into a single, easily readable block of text.

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 simple nature of the API and the presence of a mutation hint, the description is functionally complete. An agent receives all necessary information to determine if and how to call the tool correctly.

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?

While the schema is complete (100% coverage), the description adds critical semantic value by explaining the conditional requirement for the 'id' parameter based on the selected 'action' (e.g., 'open (needs id)'). This is vital context not captured by the schema alone.

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 defines the resource (sidebar) and the specific verbs it performs (open, close, toggle). It distinguishes this tool from other potential sidebars management tools by detailing the operations available within it.

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?

It provides crucial guidance by instructing the agent where to retrieve necessary parameters ('Get ids from browser_list_sidebars'), linking the tool's functionality to another necessary tool in the ecosystem.

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