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

With no annotations provided, the description carries the full burden. It communicates a listing/read-only operation scoped to the owner, which is a minimal behavioral statement. However, it does not disclose error behavior, output shape, token requirements, or whether any side effects occur.

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 a single efficient sentence with no filler, and the core action and scope are front-loaded. It could include more operational detail, but as prose it is appropriately concise.

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 lack of annotations, no output schema, and an undocumented required parameter, the description leaves too much unsaid. An agent still needs to guess what a 'tab' is, how to obtain a guest_token, what the returned data looks like, and how this relates to sibling tools like run_tab and create_tab.

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 schema has 0% description coverage and the sole required parameter guest_token is not mentioned in the description. The agent receives no explanation of what guest_token is, where it comes from, or its format, leaving the parameter semantically opaque.

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 verb ('Lists') and the resource ('tabs'), and scopes it to 'the owner's tabs (guest or session)'. This distinguishes it from sibling tools like list_tools and create_tab, though the meaning of 'guest or session' is slightly ambiguous.

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?

There is no guidance on when to use this tool instead of siblings such as run_tab, create_tab, or list_tools. The only signal is the word 'lists', so the appropriate usage context must be inferred entirely by the agent.

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