socials_set_agent_tab

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

With no annotations provided, the description must disclose behavioral traits, but it does not explain side effects (e.g., whether it changes focus, replaces the previous agent tab, or performs any navigation/seeking). 'Pin' implies a state change but the description does not clarify the impact on the browser or other tools.

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-loaded with the primary purpose, and includes a direct instruction for the parameter. 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?

For a simple one-parameter tool with no output schema, the description covers the core action and parameter source. It does not explicitly state when to use vs. alternatives, but given the sibling tool names and the clear 'existing tab' wording, the context is sufficiently complete for an agent to select and invoke 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 already defines tab_id with a description, so schema coverage is 100%. The description adds valuable semantics by specifying the source of the tab_id ('from socials_get_active_tab'), which helps the agent retrieve the correct value beyond what the schema provides.

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 function with a specific verb+resource: 'Pin an existing tab as the agent tab'. It distinguishes from siblings like open_tab (which opens a new tab) and get_agent_tab (which retrieves the current agent tab), and provides concrete examples (X, LinkedIn, Reddit, YouTube).

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 when to use the tool ('existing tab') and how to obtain the required tab_id ('Pass tab_id from socials_get_active_tab'). It lacks explicit exclusions or alternatives, but the context is clear enough for an agent to know this is for setting an already-open tab as the agent tab.

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