herdr_tabs

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, covering the safety profile. The description adds the scoping constraint that the list can be restricted to one workspace, which is useful operational context, but discloses no additional behavioral traits such as pagination, return format, or auth requirements.

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?

One short sentence with zero waste, front-loading the action ('List tabs') and then the optional scope. Every word earns its place for a tool of this simplicity.

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, read-only list operation with rich annotations and full schema coverage, the definition is nearly complete. It omits return-value details, but with no output schema and an obvious list semantic, that is a minor gap rather than a blocking one.

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 100%, and the single optional parameter workspace_id is fully described in the schema as 'Restrict to this workspace id.' The description's 'optionally in one workspace' mirrors this without adding syntax, format, or edge-case details beyond what the schema already 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?

States a specific verb and resource ('List tabs') and scopes it with 'optionally in one workspace.' This clearly distinguishes it from sibling tools like herdr_tab_create and herdr_tab_close. It does not explicitly name those alternatives, but the verb-resource pairing is 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?

Provides no when-to-use guidance or comparison to alternatives. The phrase 'optionally in one workspace' implies you can filter, but it does not say when to prefer this tool over herdr_workspaces, herdr_panes, or other list tools, nor does it state any exclusion conditions.

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