herdr_tab_list

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

With no annotations, the description must convey behavioral traits itself. It discloses the return fields and the optional workspace filter, but does not explicitly state read-only safety, no side effects, or potential ordering/pagination quirks. For a simple list operation, this is adequate but not comprehensive.

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 'List tabs', and each phrase adds essential information: optional filter and returned fields. There is zero redundancy or filler.

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 one optional parameter and full schema coverage, the description provides the key return fields (tab_id, label, pane_count, agent_status), making it functional for an agent. It omits the response shape and edge-case behavior (e.g., invalid workspace_id), but for a simple list tool this is largely adequate.

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 describes workspace_id as 'Only list tabs of this workspace (optional).' The description mirrors this by saying 'optionally filtered to a workspace' without adding extra details like format or default behavior. Since schema coverage is 100%, the description adds no additional parameter semantics beyond the baseline.

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 action ('List tabs') and the resource ('tabs'), with an optional filter by workspace. It distinguishes from sibling tools like herdr_tab_get by using 'List' and from list tools for other resources. It also previews return fields, making the purpose unambiguous.

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 usage for enumerating tabs with optional filtering but provides no explicit guidance on when to prefer this over alternatives like herdr_tab_get or herdr_pane_list. No exclusions or when-not-to-use scenarios are mentioned, leaving selection to inferred context.

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