socials_open_tab

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

With no annotations, the description carries full burden and discloses important behaviors: cross-window targeting, background default, and pin placement. It does not cover error handling or return value, but key side effects are well explained.

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?

Three sentences, each earning its place: purpose, cross-window targeting, and focus/pin behavior. No filler or redundant repetition of schema details.

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 open-url tool, the description covers purpose, targeting, and pin behavior effectively. It lacks output/return value information and error scenarios, but those are not critical for this action.

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?

Schema coverage is 100% with detailed descriptions for url (including platform examples and encoding guidance) and focus (default false). The tool description itself adds no new parameter semantics beyond the schema, so baseline 3 is appropriate.

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?

Description opens with a specific verb+resource: 'Open a URL in a new tab and pin it as the Socials agent tab.' It clearly states the primary function and differentiates from sibling tools by noting automation targets this tab by ID across tabs and windows.

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?

Provides clear operational context: default is background, focus:true switches to it, and existing pins cause same-window opening to avoid stealing the workspace. However, it does not explicitly mention when to prefer this over alternatives like socials_navigate or socials_focus_agent_tab.

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