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

Annotations already declare readOnlyHint=false, openWorldHint=true, idempotentHint=false, and destructiveHint=false, so the safety profile is covered. The one behavioral sentence about queue_audit duplicates the schema's parameter description verbatim in substance, adding nothing beyond what structured data already provides (e.g., no mention of tab lifecycle, persistence, or why a guest token is required).

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?

Two short sentences with no filler and the core action front-loaded. It is efficiently sized, though the second sentence spends real estate restating the schema.

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 mutating tool with a required undocumented credential (guest_token), no output schema, and several closely related tab siblings, the description leaves key questions unanswered: what a tab is, whether it persists, and how it relates to run_tab/watch_tab. Annotations cover the safety profile, but the operational framing is thin.

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 description coverage is 75%, so most parameters are already documented, and the baseline is 3. The description only echoes queue_audit behavior already stated in the schema and adds nothing about url, alias, or the undocumented guest_token, which is a required parameter with no description anywhere.

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 says 'Opens a saved URL', which is a vague verb that does not clearly convey that a persistent tab record is being created. It never distinguishes this tool from siblings like run_tab, watch_tab, or list_tabs, so an agent must guess which tab tool actually creates the entry.

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 only usage hint is the queue_audit=false case, which just restates a parameter default. There is no guidance on when to use create_tab versus run_tab or watch_tab, and no mention of prerequisites such as the required guest_token.

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